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

Allow for setting of isOfficialBuild when uploading intermediate artifacts #100528

Merged
merged 1 commit into from
Apr 2, 2024

Allow for the manual setting of if the build is official when uploadi…

89b29d4
Select commit
Loading
Failed to load commit list.
Merged

Allow for setting of isOfficialBuild when uploading intermediate artifacts #100528

Allow for the manual setting of if the build is official when uploadi…
89b29d4
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime-wasm-perf failed Apr 2, 2024 in 1h 28m 3s

Build #20240402.1 had test failures

Details

Tests

  • 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.24176.6/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.24176.6/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L91

.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24176.6/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item wasm.x64.micro.net9.0.Partition0 in job c20f07bf-458f-4549-a08d-7e14bb0fa9b2 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/c20f07bf-458f-4549-a08d-7e14bb0fa9b2/workitems/wasm.x64.micro.net9.0.Partition0/console

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

See this annotation in the file changed.

@azure-pipelines 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.