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

[OSX] HybridGlobalization Workaround for insufficiently sized destination buffer #88184

Merged
merged 4 commits into from
Jul 4, 2023

Add comments to make code more readable

824859e
Select commit
Loading
Failed to load commit list.
Merged

[OSX] HybridGlobalization Workaround for insufficiently sized destination buffer #88184

Add comments to make code more readable
824859e
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime-extra-platforms failed Jul 3, 2023 in 3h 25m 17s

Build #20230703.2 had test failures

Details

Tests

  • Failed: 171 (0.00%)
  • Passed: 4,449,785 (97.70%)
  • Other: 104,471 (2.29%)
  • Total: 4,554,427

Annotations

Check failure on line 6635 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-extra-platforms

Build log #L6635

Exit code 137 returned from process: file name '/usr/bin/docker', arguments 'exec -i -u 1000  -w /home/cloudtest_azpcontainer 709a28ea96c824c5cf917e0da8f543ebca49bd512763d1bb4a67d637dbfd1361 /__a/externals/node/bin/node /__w/_temp/containerHandlerInvoker.js'.

Check failure on line 6608 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-extra-platforms

Build log #L6608

Exit code 137 returned from process: file name '/usr/bin/docker', arguments 'exec -i -u 1000  -w /home/cloudtest_azpcontainer 1dd2460a269394cc64c6dd18d1f26f3916888a4bf73736932934410ce6163323 /__a/externals/node/bin/node /__w/_temp/containerHandlerInvoker.js'.

Check failure on line 114 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-extra-platforms

Build log #L114

Bash exited with code '1'.

Check failure on line 89 in .packages/microsoft.dotnet.helix.sdk/8.0.0-beta.23328.2/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-extra-platforms

.packages/microsoft.dotnet.helix.sdk/8.0.0-beta.23328.2/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets#L89

.packages/microsoft.dotnet.helix.sdk/8.0.0-beta.23328.2/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(89,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item PayloadGroup0 in job 8b81c5bd-3852-49de-bb61-68a3d5a3f596 has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/8b81c5bd-3852-49de-bb61-68a3d5a3f596/workitems/PayloadGroup0/console

Check failure on line 1 in Microsoft.Extensions.Options.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-extra-platforms

Microsoft.Extensions.Options.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.Immutable.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-extra-platforms

System.Collections.Immutable.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.ComponentModel.Primitives.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-extra-platforms

System.ComponentModel.Primitives.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.Data.Odbc.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime-extra-platforms

System.Data.Odbc.Tests.WorkItemExecution

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