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.

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

[browser] install Firefox on helix #101171

Merged
merged 1 commit into from
Apr 17, 2024

FF

de069a1
Select commit
Loading
Failed to load commit list.
Merged

[browser] install Firefox on helix #101171

FF
de069a1
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime failed Apr 17, 2024 in 2h 29m 55s

Build #20240417.13 had test failures

3 errors / 0 warnings

Details

Tests

  • Failed: 3 (0.00%)
  • Passed: 427,686 (96.64%)
  • Other: 14,876 (3.36%)
  • Total: 442,565

Annotations

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

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

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

.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24212.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item WasmTestOnBrowser-System.Text.Json.Tests in job 837db9ea-1d12-4750-bdf9-730c2b463f14 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/837db9ea-1d12-4750-bdf9-730c2b463f14/workitems/WasmTestOnBrowser-System.Text.Json.Tests/console

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

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

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

.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24212.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item WasmTestOnBrowser-System.Text.Json.Tests in job 650616dd-3762-4736-af11-ebbfc7633148 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/650616dd-3762-4736-af11-ebbfc7633148/workitems/WasmTestOnBrowser-System.Text.Json.Tests/console

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

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

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

.packages/microsoft.dotnet.helix.sdk/9.0.0-beta.24212.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item normal-System.Text.Json.Tests in job 94fccb13-5efe-4634-b039-9192a3f13347 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/94fccb13-5efe-4634-b039-9192a3f13347/workitems/normal-System.Text.Json.Tests/console

Check failure on line 1 in WasmTestOnBrowser-System.Text.Json.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

WasmTestOnBrowser-System.Text.Json.Tests.WorkItemExecution 

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

Check failure on line 1 in WasmTestOnBrowser-System.Text.Json.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

WasmTestOnBrowser-System.Text.Json.Tests.WorkItemExecution 

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

Check failure on line 1 in normal-System.Text.Json.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

normal-System.Text.Json.Tests.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