Bug 27799 - Samsung specific Runtime test failures due to System.IO.IOException
Summary: Samsung specific Runtime test failures due to System.IO.IOException
Status: RESOLVED FIXED
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 5.1
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2015-03-09 17:34 UTC by Ben Beckley
Modified: 2015-03-11 10:51 UTC (History)
1 user (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 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:
Status:
RESOLVED FIXED

Description Ben Beckley 2015-03-09 17:34:01 UTC
Experiencing Runtime test failures on 14 Samsung devices. The app successfully runs and passes 66/68 tests but fails on 1. This was with mono-android-5.1.0-12. Any insight on to what the failure is would be appreciated!

Gist of the failure:
https://gist.github.com/BenBeckley/346975babbdca09595ac

Link to the test cloud run:
https://testcloud.xamarin.com/test/xamarin.android.runtimetests_f0103f22-a381-4ba4-b2dd-6bcfcb2bc62a/?step=0_0_0&tab=console
Comment 1 Jonathan Pryor 2015-03-10 18:19:13 UTC
"Win32 IO returned 50" is ERROR_NOT_SUPPORTED, so it looks like there's another set of errors that should be ignored within the test.
Comment 2 Jonathan Pryor 2015-03-11 10:51:51 UTC
Fixed in monodroid/11268ed5 and monodroid-5.1-series/d6d182fa.