Bug 11023 - Successful unit tests throw excption in Mono.Unix.Native.Stdlib
Summary: Successful unit tests throw excption in Mono.Unix.Native.Stdlib
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: NUnit ()
Version: 4.0.1
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2013-03-09 17:29 UTC by Robert Stehwien
Modified: 2013-05-12 18:09 UTC (History)
4 users (show)

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

stacktrace of error (231.88 KB, image/png)
2013-03-09 17:29 UTC, Robert Stehwien

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 Robert Stehwien 2013-03-09 17:29:01 UTC
Created attachment 3566 [details]
stacktrace of error

The first unit tests that pass cause this error.  If all tests fail, the unit tests run.
Comment 1 jaroslav.imrich 2013-05-01 16:13:39 UTC
I've encountered exactly the same problem in Xamarin Studio 4.0.3 when running Pkcs11Interop [1] tests. These tests run without any problems in GUI application provided by NUnit- but I am not sure whether it uses Mono or .NET runtime.

[1] https://github.com/jariq/Pkcs11Interop/tree/1.1
Comment 2 jaroslav.imrich 2013-05-12 16:01:59 UTC
I've just updated to Xamarin Studio 4.0.5 (build 4) and this problem no longer occurs.
Comment 3 Mike Krüger 2013-05-12 18:09:33 UTC
Thanks for letting us know.