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

[wasm] Bump chrome for testing - linux: 125.0.6422.141, windows: 126.0.6478.36 #103204

Merged

ilonatommy merged 2 commits into main from update-chrome-version-9432414852

Jun 11, 2024

Merged

[wasm] Bump chrome for testing - linux: 125.0.6422.141, windows: 126.0.6478.36 #103204

Fix: NodeJS behaves like FF.

Azure Pipelines / runtime-wasm-perf failed Jun 10, 2024 in 1h 17m 2s

Build #20240610.1 had test failures

1 errors / 0 warnings

Details

Failed: 1 (3.13%)
Passed: 31 (96.88%)
Other: 0 (0.00%)
Total: 32

Annotations

Check failure on line 91 in .packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24306.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets

azure-pipelines / runtime-wasm-perf

.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24306.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L91

.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24306.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item wasm.x64.micro.net9.0.Partition0 in job d915d195-6601-4492-80c8-36f3db783ffa has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/d915d195-6601-4492-80c8-36f3db783ffa/workitems/wasm.x64.micro.net9.0.Partition0/console

Check failure on line 1 in wasm.x64.micro.net9.0.Partition0.WorkItemExecution

azure-pipelines / runtime-wasm-perf

wasm.x64.micro.net9.0.Partition0.WorkItemExecution

The Helix Work Item failed. Often this is due to a test crash. Please see the 'Artifacts' tab above for additional logs.

View more details on Azure Pipelines