Bug 15978 - [iOS] TimerTest, TestChange failure observed on iPodTouch 5.1.1 device and 7.0.4.pkg
Summary: [iOS] TimerTest, TestChange failure observed on iPodTouch 5.1.1 device and 7...
Status: RESOLVED DUPLICATE of bug 14305
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 7.0.4.x
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2013-11-06 20:39 UTC by GouriKumari
Modified: 2013-11-07 08:09 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:

Description GouriKumari 2013-11-06 20:39:55 UTC
Steps to reproduce:

Update system with monotouch 4cfdcfa0989c8e9fb27c0ccfa2d3f598bf9791a2 , corresponding mono and maccore.

Execute mscorlib tests on iOS device 5.1.1

Actual behaviour:
TimerTest, TestChange fails on iPodTouch 5.1.1

TestLog: https://gist.github.com/GouriKumari/d2a19eae5eecc1f1b738

Test Env:
monotouch 4cfdcfa0989c8e9fb27c0ccfa2d3f598bf9791a2
iPodtouch 5.1.1
Comment 1 Sebastien Pouliot 2013-11-07 08:09:19 UTC
It's a duplicate of #14305 but the log gives a bit more details (since the assert was changed to provide more).

*** This bug has been marked as a duplicate of bug 14305 ***