Closed aspnet-hello closed 6 years ago
Please use this workflow to address this flaky test issue, including checking applicable checkboxes and filling in the applicable "TODO" entries:
Is this actually a flaky test?
Is this test failure caused by product code flakiness? (Either this product, or another product this test depends on.)
Is it that the test itself is flaky? This includes external transient problems (e.g. remote server problems, file system race condition, etc.)
This comment was made automatically. If there is a problem contact ryanbrandenburg.
PublishAndRun_Test failed with about the same error on master. Smoke_Tests failed with about the same error on master. PublishAndRun_Test failed with about the same error on master. PublishAndRun_Test failed with about the same error on master. PublishAndRun_Test failed with about the same error on master. PublishAndRun_Test failed with about the same error on master. PublishAndRun_Test failed with about the same error on master. OpenIdConnectTestSuite failed with about the same error on master. PublishAndRun_Test failed with about the same error on master.
This comment was made automatically. If there is a problem contact ryanbrandenburg.
@pranavkm, can you please take a look at this? Thanks!
Seems like a Kestrel thing:
System.IO.FileLoadException: Could not load file or assembly 'System.Runtime.CompilerServices.Unsafe, Version=4.0.4.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'System.Runtime.CompilerServices.Unsafe, Version=4.0.4.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
at System.Memory`1.op_Implicit(Memory`1 memory)
at System.IO.Pipelines.BufferSegment.set_End(Int32 value)
at System.IO.Pipelines.BufferSegment.SetMemory(IMemoryOwner`1 memoryOwner, Int32 start, Int32 end, Boolean readOnly)
at System.IO.Pipelines.Pipe.AllocateWriteHeadUnsynchronized(Int32 sizeHint)
at System.IO.Pipelines.Pipe.GetMemory(Int32 sizeHint)
at Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.Internal.SocketConnection.<ProcessReceives>d__27.MoveNext()
Did we pick up a bad package?
DotnetRun_Tests failed with about the same error on master. OpenIdConnectTestSuite failed with about the same error on master. PublishAndRun_Test failed with about the same error on master. PublishAndRun_Test failed with about the same error on master. PublishAndRun_Test failed with about the same error on master. PublishAndRun_Test failed with about the same error on master. DotnetRun_Tests failed with about the same error on master. PublishAndRun_Test failed with about the same error on master. PublishAndRun_Test failed with about the same error on master. Smoke_Tests failed with about the same error on master. PublishAndRun_Test failed with about the same error on master. PublishAndRun_Test failed with about the same error on master. PublishAndRun_Test failed with about the same error on master. PublishAndRun_Test failed with about the same error on master. OpenIdConnectTestSuite failed with about the same error on master.
This comment was made automatically. If there is a problem contact ryanbrandenburg. There were 8 failures with about the same error on master: DotnetRun_Tests PublishAndRun_Test PublishAndRun_Test
This is the same issue as aspnet/Home#3544.
There were 8 failures with about the same error on master:
This comment was made automatically. If there is a problem contact ryanbrandenburg. There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
This comment was made automatically. If there is a problem contact ryanbrandenburg. There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
This comment was made automatically. If there is a problem contact ryanbrandenburg. There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
This comment was made automatically. If there is a problem contact ryanbrandenburg. There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
This comment was made automatically. If there is a problem contact ryanbrandenburg. There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
There were 8 failures with about the same error on master:
Fixed by resolution for https://github.com/aspnet/Home/issues/3544
This test fails occasionally with the following error:
Other tests within that build may have failed with a similar message, but they are not listed here. Check the link above for more info.
This test failed on master.
CC @mkArtakMSFT
This issue was made automatically. If there is a problem contact ryanbrandenburg.