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.

Sign up for GitHub

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

Jump to bottom

Ensure DOTNET_MaxVectorTBitwidth is interpreted as a decimal based input, not hexadecimal #88761

Merged

tannergooding merged 2 commits into dotnet:main from tannergooding:maxvectortbitwidth

Jul 13, 2023

Merged

Ensure DOTNET_MaxVectorTBitwidth is interpreted as a decimal based input, not hexadecimal #88761

Use CLRConfig::LookupOptions::ParseIntegerAsBase10 instead

Azure Pipelines / runtime (Build coreclr Pri0 Runtime Tests Run osx x64 checked) failed Jul 12, 2023 in 48m 37s

Build coreclr Pri0 Runtime Tests Run osx x64 checked failed

1 errors / 0 warnings

Annotations

Check failure on line 42 in .packages/microsoft.dotnet.helix.sdk/8.0.0-beta.23328.2/tools/azure-pipelines/AzurePipelines.MultiQueue.targets

azure-pipelines / runtime (Build coreclr Pri0 Runtime Tests Run osx x64 checked)

.packages/microsoft.dotnet.helix.sdk/8.0.0-beta.23328.2/tools/azure-pipelines/AzurePipelines.MultiQueue.targets#L42

.packages/microsoft.dotnet.helix.sdk/8.0.0-beta.23328.2/tools/azure-pipelines/AzurePipelines.MultiQueue.targets(42,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Test JIT/opt/Add/IntAdd/IntAdd.cmd has failed. Check the Test tab or this console log: https://helix.dot.net/api/2019-06-17/jobs/3b9a7a9d-d37d-4ab0-87be-b0a5b2e6e2d4/workitems/JIT.opt/console

View more details on Azure Pipelines