-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hang/timeout in tests for Browser wasm Release AllSubsets_Mono #40550
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @BrzVlad |
cc @lewing |
I've noticed System.Runtime tests are huge and they take an average of 9-12 mins. The timeout in helix is 12 minutes. Maybe we should bump the timeout for wasm workitems? |
Actually looking at the timestamps it looks like a legit hang. It just ran for 3 mins.
|
cc @vargaz |
The main log has
Hence my assumption is that between the 17:18 and 17:30 timestamp there was a test jammed. (?) |
it is likely #40214 |
@lewing another CI hang this time in System.Collections.NonGeneric.Tests
There is no dump so I'm not sure how we can tell whether it's #40214. was in #40729 |
@danmosemsft we are actively working some wasm GC related corruption problems. Blazor will ship using the same GC mode it did in 3.2 which should not have these problems. We plan to keep the on demand GC mode enabled for the runtime tests. |
Thanks @lewing I'm trying to improve my kusto querying powers, so I did
says
which I think means that the hangs are not a super big problem. |
@danmosemsft @lewing - considering hangs are not a big issue, can we remove the blocking-clean-ci tag. We are working on GC improvements, but will ship as full GC disabled just like 3.2 release. We will keep chipping away at fixing issues found via tests, but not targeting 5.0 RC submissions unless we identify a very nasty issue. Moving this to 6.0 Milestone and removing the blocking-clean-ci tag maybe the right approach here. |
Closing as I don't see any recent occurences of this issue. |
https://helix.dot.net/api/2019-06-17/jobs/e7fed000-94bb-45ab-950e-2403ad3753b5/workitems/System.Runtime.Tests/console
https://dev.azure.com/dnceng/public/_build/results?buildId=761619&view=logs&jobId=108d2c4a-8a62-5a58-8dad-8e1042acc93c&j=108d2c4a-8a62-5a58-8dad-8e1042acc93c&t=09a92b4c-3493-52a9-1172-0680b62c9e30
last lines of console
I guess whatever the next test was (not logged) just hung and then it timed out 12 mins later? Can we make it log the test before it starts it, so we have a clue which?
The text was updated successfully, but these errors were encountered: