Bug 13955 - [iOS] MSCorlib test failures reported on device
Summary: [iOS] MSCorlib test failures reported on device
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 6.4.0
Hardware: PC Mac OS
: --- normal
Target Milestone: 6.4.x (post async)
Assignee: Bugzilla
Depends on:
Reported: 2013-08-13 11:30 UTC by GouriKumari
Modified: 2013-08-13 15:16 UTC (History)
2 users (show)

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 Developer Community or GitHub 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:

Comment 1 Sebastien Pouliot 2013-08-13 11:56:27 UTC
> Also, on checking out mono there are
> certain unstaged changes which are related to test failures.

There should not be. That means the tests you compiled are not what we expect them to be (the mono revision you checked out) and all bets are off (if those file were not updated then it's a clue something changed in them).

I do not know which s script(s) / command(s) you're using but you need to fix them so that the mono and monotuch checkout are *pristine* before running the tests. Please try again with clean trees.
Comment 2 GouriKumari 2013-08-13 15:15:44 UTC
After doing a hard reset of mono, the mscorlib tests are executing successfully in QA test lanes. I am marking this bug as "Resolved Invalid", since this was a bug in QA MT test lane scripts.