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

Update DbDataSource.cs #112609

Merged
merged 1 commit into from
Feb 18, 2025

Update DbDataSource.cs

0783a4b
Select commit
Loading
Failed to load commit list.
Merged

Update DbDataSource.cs #112609

Update DbDataSource.cs
0783a4b
Select commit
Loading
Failed to load commit list.
Azure Pipelines / runtime failed Feb 16, 2025 in 4h 3m 16s

Build #20250216.7 had test failures

Details

Tests

  • Failed: 6 (0.00%)
  • Passed: 3,022,002 (98.21%)
  • Other: 55,128 (1.79%)
  • Total: 3,077,136

Annotations

Check failure on line 44 in .packages/microsoft.dotnet.helix.sdk/10.0.0-beta.25106.4/tools/azure-pipelines/AzurePipelines.MultiQueue.targets

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

.packages/microsoft.dotnet.helix.sdk/10.0.0-beta.25106.4/tools/azure-pipelines/AzurePipelines.MultiQueue.targets#L44

.packages/microsoft.dotnet.helix.sdk/10.0.0-beta.25106.4/tools/azure-pipelines/AzurePipelines.MultiQueue.targets(44,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Test System.Diagnostics.Tests.ProcessThreadTests.TestStartTimeProperty has failed. Check the Test tab or this console log: https://helix.dot.net/api/2019-06-17/jobs/4c5cae7d-5b48-47d9-a4ea-a5e7d333aff1/workitems/System.Diagnostics.Process.Tests/console

Check failure on line 52 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Build log #L52

The Operation will be canceled. The next steps may not contain expected logs.

Check failure on line 53 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

Build log #L53

The operation was canceled.

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

.packages/microsoft.dotnet.helix.sdk/10.0.0-beta.25106.4/tools/Microsoft.DotNet.Helix.Sdk.MultiQueue.targets(91,5): error : (NETCORE_ENGINEERING_TELEMETRY=Test) Work item WasmTestOnChrome-MT-System.Net.Http.Functional.Tests in job 6d9f3ba4-7dcb-4fd6-aa98-ced31ffd76eb has failed.
Failure log: https://helix.dot.net/api/2019-06-17/jobs/6d9f3ba4-7dcb-4fd6-aa98-ced31ffd76eb/workitems/WasmTestOnChrome-MT-System.Net.Http.Functional.Tests/console

Check failure on line 1 in System.Diagnostics.Tests.ProcessThreadTests.TestStartTimeProperty

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

System.Diagnostics.Tests.ProcessThreadTests.TestStartTimeProperty

Assert.Single() Failure: The collection did not contain any matching items
Expected:   (predicate expression)
Collection: [System.Diagnostics.ProcessThread, System.Diagnostics.ProcessThread, System.Diagnostics.ProcessThread, System.Diagnostics.ProcessThread, System.Diagnostics.ProcessThread, ···]
Raw output
   at System.Diagnostics.Tests.ProcessThreadTests.<>c__DisplayClass4_2.<TestStartTimeProperty>b__0() in /_/src/libraries/System.Diagnostics.Process/tests/ProcessThreadTests.cs:line 156
   at System.Threading.Tasks.Task.InnerInvoke() in /_/src/libraries/System.Private.CoreLib/src/System/Threading/Tasks/Task.cs:line 2397
   at System.Threading.Tasks.Task.<>c.<.cctor>b__292_0(Object obj) in /_/src/libraries/System.Private.CoreLib/src/System/Threading/Tasks/Task.cs:line 2385
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) in /_/src/libraries/System.Private.CoreLib/src/System/Threading/ExecutionContext.cs:line 179
--- End of stack trace from previous location ---
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) in /_/src/libraries/System.Private.CoreLib/src/System/Threading/ExecutionContext.cs:line 203
   at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread) in /_/src/libraries/System.Private.CoreLib/src/System/Threading/Tasks/Task.cs:line 2343
--- End of stack trace from previous location ---
   at System.Diagnostics.Tests.ProcessThreadTests.TestStartTimeProperty() in /_/src/libraries/System.Diagnostics.Process/tests/ProcessThreadTests.cs:line 149
--- End of stack trace from previous location ---

Check failure on line 1 in System.Net.Sockets.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

System.Net.Sockets.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 WasmTestOnChrome-MT-System.Net.Http.Functional.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

WasmTestOnChrome-MT-System.Net.Http.Functional.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 WasmTestOnChrome-MT-System.Net.WebSockets.Client.Tests.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / runtime

WasmTestOnChrome-MT-System.Net.WebSockets.Client.Tests.WorkItemExecution

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