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

[release/6.1] Update dependencies from dotnet/arcade #5529

Merged
merged 2 commits into from
May 8, 2024

Update dependencies from https://github.com/dotnet/arcade build 20240…

a202620
Select commit
Loading
Failed to load commit list.
Merged

[release/6.1] Update dependencies from dotnet/arcade #5529

Update dependencies from https://github.com/dotnet/arcade build 20240…
a202620
Select commit
Loading
Failed to load commit list.
Azure Pipelines / dotnet-wcf-ci succeeded May 8, 2024 in 23m 44s

Build #20240507.9 had test failures

0 errors / 0 warnings

Details

Tests

  • Failed: 80 (0.35%)
  • Passed: 20,844 (91.61%)
  • Other: 1,828 (8.03%)
  • Total: 22,752

Annotations

Check failure on line 1 in ExpectedExceptionTests.DuplexCallbackDebugBehavior_IncludeExceptionDetailInFaults_True

See this annotation in the file changed.

@azure-pipelines azure-pipelines / dotnet-wcf-ci

ExpectedExceptionTests.DuplexCallbackDebugBehavior_IncludeExceptionDetailInFaults_True 

Test failed

Check failure on line 1 in HttpsTests.WebSocket_RequestReply_CertificateCredentials

See this annotation in the file changed.

@azure-pipelines azure-pipelines / dotnet-wcf-ci

HttpsTests.WebSocket_RequestReply_CertificateCredentials 

System.ServiceModel.CommunicationException : The server returned status code '404' when status code '101' was expected.
---- System.Net.WebSockets.WebSocketException : The server returned status code '404' when status code '101' was expected.
Raw output 
   at System.ServiceModel.Channels.ClientWebSocketTransportDuplexSessionChannel.TryConvertAndThrow(WebSocketException ex) in /_/src/System.ServiceModel.Http/src/System/ServiceModel/Channels/ClientWebSocketTransportDuplexSessionChannel.cs:line 266
   at System.ServiceModel.Channels.ClientWebSocketTransportDuplexSessionChannel.OnOpenAsync(TimeSpan timeout) in /_/src/System.ServiceModel.Http/src/System/ServiceModel/Channels/ClientWebSocketTransportDuplexSessionChannel.cs:line 115
   at System.ServiceModel.Channels.CommunicationObject.OnOpenAsyncInternal(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.System.ServiceModel.IAsyncCommunicationObject.OpenAsync(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.OnOpenAsync(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.OnOpenAsyncInternal(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.System.ServiceModel.IAsyncCommunicationObject.OpenAsync(TimeSpan timeout)
   at System.Runtime.TaskHelpers.WaitForCompletion(Task task)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
   at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(MethodCall methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(MethodInfo targetMethod, Object[] args)
   at generatedProxy_2.Echo(String )
   at HttpsTests.WebSocket_RequestReply_CertificateCredentials() in /_/src/System.Private.ServiceModel/tests/Scenarios/Security/TransportSecurity/Https/HttpsTests.4.1.0.cs:line 494
----- Inner Stack Trace -----
   at System.Net.WebSockets.WebSocketHandle.ConnectAsync(Uri uri, CancellationToken cancellationToken, ClientWebSocketOptions options)
   at System.Net.WebSockets.ClientWebSocket.ConnectAsyncCore(Uri uri, CancellationToken cancellationToken)
   at System.ServiceModel.Channels.ClientWebSocketTransportDuplexSessionChannel.OnOpenAsync(TimeSpan timeout) in /_/src/System.ServiceModel.Http/src/System/ServiceModel/Channels/ClientWebSocketTransportDuplexSessionChannel.cs:line 75

Check failure on line 1 in HttpsTests.WebSocket_ServerCertificateValidation

See this annotation in the file changed.

@azure-pipelines azure-pipelines / dotnet-wcf-ci

HttpsTests.WebSocket_ServerCertificateValidation 

System.ServiceModel.CommunicationException : The server returned status code '404' when status code '101' was expected.
---- System.Net.WebSockets.WebSocketException : The server returned status code '404' when status code '101' was expected.
Raw output 
   at System.ServiceModel.Channels.ClientWebSocketTransportDuplexSessionChannel.TryConvertAndThrow(WebSocketException ex) in /_/src/System.ServiceModel.Http/src/System/ServiceModel/Channels/ClientWebSocketTransportDuplexSessionChannel.cs:line 266
   at System.ServiceModel.Channels.ClientWebSocketTransportDuplexSessionChannel.OnOpenAsync(TimeSpan timeout) in /_/src/System.ServiceModel.Http/src/System/ServiceModel/Channels/ClientWebSocketTransportDuplexSessionChannel.cs:line 115
   at System.ServiceModel.Channels.CommunicationObject.OnOpenAsyncInternal(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.System.ServiceModel.IAsyncCommunicationObject.OpenAsync(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.OnOpenAsync(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.OnOpenAsyncInternal(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.System.ServiceModel.IAsyncCommunicationObject.OpenAsync(TimeSpan timeout)
   at System.Runtime.TaskHelpers.WaitForCompletion(Task task)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
   at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(MethodCall methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(MethodInfo targetMethod, Object[] args)
   at generatedProxy_2.Echo(String )
   at HttpsTests.WebSocket_ServerCertificateValidation() in /_/src/System.Private.ServiceModel/tests/Scenarios/Security/TransportSecurity/Https/HttpsTests.4.1.0.cs:line 557
----- Inner Stack Trace -----
   at System.Net.WebSockets.WebSocketHandle.ConnectAsync(Uri uri, CancellationToken cancellationToken, ClientWebSocketOptions options)
   at System.Net.WebSockets.ClientWebSocket.ConnectAsyncCore(Uri uri, CancellationToken cancellationToken)
   at System.ServiceModel.Channels.ClientWebSocketTransportDuplexSessionChannel.OnOpenAsync(TimeSpan timeout) in /_/src/System.ServiceModel.Http/src/System/ServiceModel/Channels/ClientWebSocketTransportDuplexSessionChannel.cs:line 75

Check failure on line 1 in Client.ExpectedExceptions.IntegrationTests.dll.WorkItemExecution

See this annotation in the file changed.

@azure-pipelines azure-pipelines / dotnet-wcf-ci

Client.ExpectedExceptions.IntegrationTests.dll.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