Skip to content
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

Move jitopt and rpo experiments to PerfVipers #102575

Merged
merged 2 commits into from
May 23, 2024

Remove rpolayout experiment

72d8f39
Select commit
Loading
Failed to load commit list.
Merged

Move jitopt and rpo experiments to PerfVipers #102575

Remove rpolayout experiment
72d8f39
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime-wasm-perf failed May 22, 2024 in 54m 46s

Build #20240522.2 had test failures

Details

Tests

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

Annotations

Check failure on line 10 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-wasm-perf

Build log #L10

Path does not exist: /mnt/vss/_work/1/a/artifacts/log

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

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-wasm-perf

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

.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24266.1/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item release.Partition0 in job c4956423-de1f-4489-a03b-21e1cf4dc1d1 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/c4956423-de1f-4489-a03b-21e1cf4dc1d1/workitems/release.Partition0/console

Check failure on line 1 in release.Partition0.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-wasm-perf

release.Partition0.WorkItemExecution

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