Bug 46683 - Recurring hang in System.Xaml on CI
Summary: Recurring hang in System.Xaml on CI
Status: RESOLVED ANSWERED
Alias: None
Product: Class Libraries
Classification: Mono
Component: System (show other bugs)
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Alexander Köplinger [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2016-11-09 22:29 UTC by Andi McClure
Modified: 2018-02-22 22:05 UTC (History)
4 users (show)

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


Attachments

Description Andi McClure 2016-11-09 22:29:02 UTC
Four times in the last week there has been a hang in the System.Xaml in the CI tests. XamlBackgroundReader tests. Two on Linux/Intel64, two on Linux/Intel32. The most recent was today.

There is a set of tests that all call into a ReadTest() function, which does nothing but take in a path and reads it in the background. The failure is always one of these tests. The hang always occurs in XamlBackgroundReader.Read (), which WaitOnes on its ManualResetEvent and never gets woken up. See:

https://jenkins.mono-project.com/job/test-mono-mainline-linux/label=ubuntu-1404-i386/1136/parsed_console/log_content.html#WARNING2
https://jenkins.mono-project.com/job/test-mono-mainline-linux/label=ubuntu-1404-amd64/1107/parsed_console/log_content.html#WARNING1
https://jenkins.mono-project.com/job/test-mono-mainline-linux/label=ubuntu-1404-amd64/1131/parsed_console/log_content.html#WARNING1

Koeplinger reviewed and believed this is an issue for the class library team.
Comment 1 Marek Safar 2018-02-22 22:05:21 UTC
We track flaky issues differently now

Notice (2018-05-21): bugzilla.xamarin.com will be switching to read-only mode on Thursday, 2018-05-25 22:00 UTC.

Please join us on Visual Studio Developer Community and GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs and copy them to the new locations as needed for follow-up. The See Also field on each Bugzilla bug will be updated with a link to its new location when applicable.

After Bugzilla is read-only, if you have new information to add for a bug that does not yet have a matching issue on Developer Community or GitHub, you can create a follow-up issue in the new location. Copy and paste the title and description from this bug, and then add your new details. You can get a pre-formatted version of the title and description here:

In special cases you might also want the comments:

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.

Note You need to log in before you can comment on or make changes to this bug.