Remove DOTNET_EnableAVX512=0 from Blazor E2E test pipeline #63269
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR removes the
DOTNET_EnableAVX512=0
environment variable from the Azure DevOps pipeline configuration in.azure/pipelines/components-e2e-tests.yml
.The environment variable was previously added as a temporary workaround for AVX512-related issues in the .NET runtime/JIT compiler. With the current SDK version (10.0.100-preview.7.25380.108), this workaround is no longer necessary and can be safely removed.
Changes:
DOTNET_EnableAVX512: 0
environment variable from the "Run E2E tests" stepDOTNET_EnableAVX512: 0
environment variable from the "Run Quarantined E2E tests" stepThe removal was verified to maintain valid YAML syntax and no other references to this environment variable exist in the repository.
Fixes #63105.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.