-
Notifications
You must be signed in to change notification settings - Fork 5k
Add Sve.IsSupported check in test #116026
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds a safeguard in the SVE tests to only run certain test functions if SVE support is available, addressing issue #115988.
- Added an if-check for Sve.IsSupported in the test method
- Wrapped the existing test functionality in a conditional block to avoid execution on unsupported platforms
Xor(); | ||
Or(); | ||
ConditionalSelect(); | ||
if (Sve.IsSupported) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider marking the test as skipped using xUnit's Skip parameter on the [Fact] attribute instead of conditionally branching within the test. This approach would provide clearer test reporting when SVE is not supported.
Copilot uses AI. Check for mistakes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you give an example on how to do it?
@a74nh PTAL |
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
/azp run runtime-coreclr jitstress-isas-arm |
Azure Pipelines successfully started running 1 pipeline(s). |
@dotnet/jit-contrib |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm guessing the jitstress-isas-arm
failure is unrelated?
/ba-g failures are related to #116030. |
Fixes: #115988