Closed ryanbrandenburg closed 6 years ago
This error (or a similarly non-specific error) also affects PublishAndRun_Test.
NtlmAuthenticationTest failed again.
NtlmAuthenticationTest failed again.
NtlmAuthenticationTest failed again.
Smoke_Tests failed again.
Smoke_Tests failed again.
OpenIdConnectTestSuite failed again.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed with about the same error. Smoke_Tests failed with about the same error. Smoke_Tests failed with about the same error. Smoke_Tests failed with about the same error. Smoke_Tests failed with about the same error. Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Smoke_Tests failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
PublishAndRun_Test failed with about the same error on master.
This comment was made automatically. If there is a problem contact ryanbrandenburg.
NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on 2.2. NtlmAuthenticationTest failed with about the same error on 2.2. NtlmAuthenticationTest failed with about the same error on 2.2. NtlmAuthenticationTest failed with about the same error on 2.2. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on 2.2. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on 2.2. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on 2.2. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on 2.2. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master.
This comment was made automatically. If there is a problem contact ryanbrandenburg.
NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on 2.2. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on 2.2. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master.
This comment was made automatically. If there is a problem contact ryanbrandenburg.
NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master. NtlmAuthenticationTest failed with about the same error on master.
This comment was made automatically. If there is a problem contact ryanbrandenburg.
DotnetRun_Tests failed with about the same error on master.
This comment was made automatically. If there is a problem contact ryanbrandenburg.
@mkArtakMSFT I think MusicStore falls under the MVC team, assigning to you to triage.
Thanks @ryanbrandenburg. @dougbu, can you please fix this? Thanks!
DotnetRun_Tests
failure 18 hours ago (above) was a RequestTimeout
with Kestrel. That failure looks very much like aspnet/KestrelHttpServer#2850 and I've therefore reopened the bug. @halter73 please confirm the fix for that bug was correctly merged into the master
branch.
In particular, note the short period covered in the following logging:
| [36.737s] Microsoft.AspNetCore.Server.IntegrationTesting.SelfHostDeployer Information: dotnet stdout: Now listening on: http://127.0.0.1:63428
| [36.737s] Microsoft.AspNetCore.Server.IntegrationTesting.SelfHostDeployer Information: dotnet stdout: Application started. Press Ctrl+C to shut down.
| [36.738s] Microsoft.AspNetCore.Server.IntegrationTesting.SelfHostDeployer Information: Application ready at URL: http://127.0.0.1:63428/
| [36.739s] DotnetRunTests Warning: Retry count 1..
| [38.208s] Microsoft.AspNetCore.Server.IntegrationTesting.SelfHostDeployer Information: dotnet stdout: \x1b[40m\x1b[32minfo\x1b[39m\x1b[22m\x1b[49m: Microsoft.AspNetCore.Server.Kestrel[17]
| [38.208s] Microsoft.AspNetCore.Server.IntegrationTesting.SelfHostDeployer Information: dotnet stdout: Connection id "0HLGP17B4BLVD" bad request data: "Reading the request headers timed out."
| [38.209s] Microsoft.AspNetCore.Server.IntegrationTesting.SelfHostDeployer Information: dotnet stdout: Microsoft.AspNetCore.Server.Kestrel.Core.BadHttpRequestException: Reading the request headers timed out.
On the other hand, the following error message shows up in the error page displayed in al of the other August failures I checked:
Cannot add duplicate collection entry of type 'add' with unique key attribute 'name' set to 'aspNetCore'
and all relate to deploying into IIS Express. The deployer has since changed significantly and it appears those failures are now resolved.
@halter73 if you agree this is a variant of aspnet/KestrelHttpServer#2850, please take this issue. If not, please suggest where I should look instead.
/cc @davidfowl
This test fails occasionally with the following error: