Bug 12545 - Unable to run monotouch-test with gsharedvt
Summary: Unable to run monotouch-test with gsharedvt
Status: RESOLVED FIXED
Alias: None
Product: Runtime
Classification: Mono
Component: General ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Rodrigo Kumpera
URL:
Depends on:
Blocks:
 
Reported: 2013-06-04 16:38 UTC by PJ
Modified: 2017-08-28 15:05 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description PJ 2013-06-04 16:38:24 UTC
Steps:
git clone git@github.com:xamarin/release-scripts
git clone git@github.com:xamarin/QualityAssurance
git clone git@github.com:xamarin/monotouch
cd ../
cp release-scripts/wrench/release.make .
make -f release-scripts/wrench/QA/monotouch/Makefile .produce-config-monotouch-test
make -f release-scripts/wrench/QA/monotouch/Makefile .test-monotouch-test_gsharedvt

Output:
https://gist.github.com/pjbeaman/1c49f74b89bc9eb28c65

.csproj diff:
https://gist.github.com/pjbeaman/3feaced57a2421b0b4b2


Using:
mono 3.0.10 ((no/eff4cb5 Sat Apr 13 19:24:30 EDT 2013)
mtouch 6.3.7.2 (54d201d)
Comment 1 Rodrigo Kumpera 2013-06-05 14:39:02 UTC
This has been fixed with in mono 3.0.12.