[Mono-dev] Mono CI weather report 11/9
anmccl at microsoft.com
Wed Nov 9 22:31:48 UTC 2016
What this is: The Mono team has a CI (continuous integration) system which builds and runs automated tests on every commit checked in to git (specifically the master branch). We have a test log viewer<https://jenkins.mono-project.com/view/All/job/jenkins-testresult-viewer/Test_Result_View/> on Jenkins that tracks the results (currently only accessible to github project admins, sorry). Once a week I sweep through and write an email with a list of the most frequently-failing automated tests.
Although we are currently red on every lane, in terms of unique issues we're actually doing a lot better than we were last week.
Issues four and five are new and need a volunteer.
Here are the top failures currently making Jenkins builds fail:
1. MonoTests.runtime.appdomain failures [Effectively new]
Last week, it was discovered there were a few tests that were not being run (or possibly were not having their errors correctly included in the collated results). Those tests have been re-enabled and are now failing on every build on every lane. They are MonoTests.runtime.appdomain-threadpool-unload.exe_timedout, MonoTests.runtime.appdomain-unload.exe_timedout, MonoTests.runtime.appdomain-thread-abort.exe, MonoTests.runtime.appdomain-unload.exe. This is being looked at by Ludovic Henry and Aleksey Kliger and they are preparing a fix. We will likely disable these tests for PRs soon.
2. ThreadAbortException in System.Threading.Timer+Scheduler.SchedulerThread (the "List`1 issue") [Existing]
Filed as https://bugzilla.xamarin.com/show_bug.cgi?id=43320 , currently assigned to Rodrigo.
This occurs in many different places but the crash message always looks the same.
System.TypeInitializationException: The type initializer for 'System.Collections.Generic.List`1' threw an exception. ---> System.Threading.ThreadAbortException
--- End of inner exception stack trace ---
at System.Threading.Timer+Scheduler.SchedulerThread () [0x0000f] in <filename unknown>:0
at System.Threading.ThreadHelper.ThreadStart_Context (System.Object state) [0x00017] in <filename unknown>:0
at System.Threading.ExecutionContext.RunInternal (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x0008d] in <filename unknown>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state, System.Boolean preserveSyncCtx) [0x00000] in <filename unknown>:0
at System.Threading.ExecutionContext.Run (System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state) [0x00031] in <filename unknown>:0
at System.Threading.ThreadHelper.ThreadStart () [0x0000b] in <filename unknown>:0
[MVID] 0deb57f9de664ff681556c641423618d 0,1,2,3,4,5
[ERROR] FATAL UNHANDLED EXCEPTION: Nested exception trying to figure out what went wrong
Some places this failure is seen include MonoTests.gshared.generic-marshalbyref.2.exe, MonoTests.runtime.bug-415577.exe, and as an unknown-test failure when a test suite (such as mcs/class/corlib) is shutting down.
https://jenkins.mono-project.com/job/test-mono-mainline/label=osx-i386/4656/parsed_console/log_content.html#WARNING1 (test shutdown)
3. MonoTests.System.Net.Sockets.SocketTest.SendAsyncFile [Existing]
Filed as https://bugzilla.xamarin.com/show_bug.cgi?id=43172 , currently unassigned.
This has been failing for a very long time. It only occurs on Linux but on Linux it fails over 20% of the time. (It has also been seen on Android.) It is possible this is only an issue in CI (see akoeplinger note in bug).
The failure is consistent and looks like:
System.Exception : Could not abort registered blocking threads before closing socket.
at System.Net.Sockets.SafeSocketHandle.RegisterForBlockingSyscall () [0x00057] in /mnt/jenkins/workspace/test-mono-mainline-linux/label/ubuntu-1404-amd64/mcs/class/System/System.Net.Sockets/SafeSocketHandle.cs:114
at System.Net.Sockets.Socket.SendFile_internal (System.Net.Sockets.SafeSocketHandle safeHandle, System.String filename, System.Byte pre_buffer, System.Byte post_buffer, System.Net.Sockets.TransmitFileOptions flags) [0x00000] in /mnt/jenkins/workspace/test-mono-mainline-linux/label/ubuntu-1404-amd64/mcs/class/System/System.Net.Sockets/Socket.cs:2944
at System.Net.Sockets.Socket.SendFile (System.String fileName, System.Byte preBuffer, System.Byte postBuffer, System.Net.Sockets.TransmitFileOptions flags) [0x00028] in /mnt/jenkins/workspace/test-mono-mainline-linux/label/ubuntu-1404-amd64/mcs/class/System/System.Net.Sockets/Socket.cs:2893
4. MonoTests.Microsoft.CSharp.CSharpCodeProviderTest.CompileFromDomBatch_NotInMemory [New]
Filed as https://bugzilla.xamarin.com/show_bug.cgi?id=46679 . Three failures in one week after never having been seen before. Appears to be a runtime issue. Symptom looks like:
* Assertion at threadpool-ms.c:709, condition `cleanup_semaphore' not met
Not assigned. Log links in bug.
5. System.Xaml hangs [New]
Filed as https://bugzilla.xamarin.com/show_bug.cgi?id=46683 . Four failures in a week, I don't remember seeing this before. There is a set of Xaml tests which is hanging in XamlBackgroundReader.Read (), waiting on a ManualResetEvent that never triggers. Appears to be a class library issue.
Not assigned. Log links in bug.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list