-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
QuaternionTests failures in release/5.0 on ARM64 CoreCLR Checked Alpine. #41108
Comments
Tagging subscribers to this area: @tannergooding, @pgovind |
I don't see relevant changes in Quaternion or the tests ... Can't see the history here -- @dotnet/dnceng why does this query not bring up the results above? Is there a delay?
|
Any delay in Kusto results is a few minutes, I think that join just only finds jobs. Checking out the TestResults table for that failure, it made it into Kusto at 2020-08-19 20:41:56.6987374 and the work item finished running 33 seconds prior. |
Maybe I need lunch then, as this doesn't find them either
|
gives me 76 results. Perhaps you need to reconnect to the cluster? (Edit: To be clear your version does too, I just hacked up what I already had to match) |
Right, I get the 76 but they are all "EntryPointNotFoundException". |
Perhaps I've not eaten enough. What are you looking for? I'd generally start where it failed once in the way you're interested in (getting its work item id) and go from there to figure out the disconnect. |
I have also noticed that everything listed in that kusto query happened on the same day. Could to be that the other pipelines aren't publishing the data to Kusto? |
What I was trying to achieve was: find out when the failure shown above started, and whether it's in master as well. I'm trying to learn how to do these things so I don't have to ask people to figure it out for me 😺 |
The test wasn't disabled was it? I don't see the failure in any recent runs. |
Doesn't appear to be disabled. |
Failed again on
|
The failure identified by @am11 is the only one I see in the last 30 days. |
Looking at the test https://github.com/dotnet/runtime/blob/master/src/libraries/System.Numerics.Vectors/tests/QuaternionTests.cs#L393-L411, this shouldn't ever produce If someone can indicate which Linux distro we are using for the |
Given that this is very intermittent failure, it may be a bug in the thread suspension for GC corrupting registers. |
It happened on Alpine Linux 3.12 aarch64. The Helix CI container instance can be ran locally with: $ docker run -it mcr.microsoft.com/dotnet-buildtools/prereqs:alpine-3.12-helix-arm64v8-20200602002604-25f8a3e |
No failures since October. I'm closing, since it seems happy now. Yes I know it was kinda intermittent, but the gap between the previous "it's fine, closing" and failure, and the gap between the last failure and today, are pretty big. I'm sure this comment will come back and bite me eventually |
release/5.0
https://dev.azure.com/dnceng/public/_build/results?buildId=779018&view=ms.vss-test-web.build-test-results-tab&runId=24416968&resultId=149262&paneView=debug
net5.0-Linux-Release-arm64-CoreCLR_checked-(Alpine.312.Arm64.Open)Ubuntu.1804.ArmArch.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:alpine-3.12-helix-arm64v8-20200602002604-25f8a3e
Runfo Tracking Issue: Runtime QuaternionTests tests
Build Result Summary
The text was updated successfully, but these errors were encountered: