-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Test failure in System.Numerics.Tensors.Tests.SingleGenericTensorPrimitives.SpanDestinationFunctions_SpecialValues #101731
Comments
Tagging subscribers to this area: @dotnet/area-system-numerics |
Tagging subscribers to this area: @dotnet/area-system-numerics-tensors |
It looks similar to #97297. |
Looks similar in runtime-coreclr libraries-jitstressregs
|
@tannergooding, PTAL. |
I can take a look and see if I can find an initial root cause, but I expect this is likely a JIT issue and unrelated to the libraries side of things. CC. @jeffhandley |
It is now failing in Runtime pipeline as well. Please see the Known issue report above. |
It is failing on #101767 with the fix. |
e.g.
|
I'm not able to reproduce the failure locally, on a machine with or without AVX512. My best guess is that in some edge case scenario the code is calling the fallback instead of allowing the intrinsic implementation to kick in. Changing it to be |
Should we disable this test for now? it's been blocking clean CI for two weeks now (e.g. I've just hit it in #102132) |
The issue is fixed with #102098 and so disabling shouldn't be needed, just final sign-off If, for whatever reason, the test still shows as flaky somewhere after then I think we can disable it then |
Failed in runtime-coreclr libraries-jitstress2-jitstressregs
Known Issue Error Message
Fill the error message using step by step known issues guidance.
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=660140
Error message validated:
[GenericFloatingPointNumberTensorPrimitivesTests
1.SpanDestinationFunctions_SpecialValues`]Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 5/1/2024 3:48:58 AM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: