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

[wasm] Bump chrome for testing - linux: 124.0.6367.201, windows: 124.0.6367.201 #102119

Merged
merged 1 commit into from
May 13, 2024

Automated bump of chrome version

7ef9ea2
Select commit
Loading
Failed to load commit list.
Merged

[wasm] Bump chrome for testing - linux: 124.0.6367.201, windows: 124.0.6367.201 #102119

Automated bump of chrome version
7ef9ea2
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime failed May 12, 2024 in 3h 3m 22s

Build #20240511.38 had test failures

12 errors / 0 warnings

Details

Tests

  • Failed: 10 (0.00%)
  • Passed: 614,464 (96.88%)
  • Other: 19,794 (3.12%)
  • Total: 634,268

Annotations

Check failure on line 91 in .packages\microsoft.dotnet.helix.sdk\9.0.0-beta.24253.1\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.24253.1\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L91 

.packages\microsoft.dotnet.helix.sdk\9.0.0-beta.24253.1\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item chrome-DebuggerTests.DateTimeTestsEFIGS in job 68efcc63-b691-4f04-b0d9-cae059b78191 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/68efcc63-b691-4f04-b0d9-cae059b78191/workitems/chrome-DebuggerTests.DateTimeTestsEFIGS/console

Check failure on line 10 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Build log #L10 

Path does not exist: D:\a\_work\1\a\artifacts\log

Check failure on line 10 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Build log #L10 

Path does not exist: D:\a\_work\1\a\artifacts\log

Check failure on line 91 in .packages\microsoft.dotnet.helix.sdk\9.0.0-beta.24253.1\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.24253.1\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L91 

.packages\microsoft.dotnet.helix.sdk\9.0.0-beta.24253.1\tools\Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item Invariant.Tests in job b01d78cd-f92f-4053-bb12-78c6334dc6f8 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/b01d78cd-f92f-4053-bb12-78c6334dc6f8/workitems/Invariant.Tests/console

Check failure on line 1 in Invariant.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Invariant.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 System.Buffers.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

System.Buffers.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 System.Collections.Specialized.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

System.Collections.Specialized.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 System.Collections.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

System.Collections.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