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.
HelloWorld failed with about the same error on master. ResponseCompression_AppCompression failed with about the same error on master. ResponseCompression_AppAndHostCompression failed with about the same error on master. ResponseCompression_AppCompression failed with about the same error on master. ResponseCompression_NoCompression failed with about the same error on master. ResponseCompression_NoCompression failed with about the same error on master. ResponseCompression_AppAndHostCompression failed with about the same error on master. ResponseCompression_AppAndHostCompression failed with about the same error on master. ResponseCompression_AppAndHostCompression failed with about the same error on master.
This comment was made automatically. If there is a problem contact ryanbrandenburg.
@muratg can you assign?
HelloWorld failed with about the same error on master. HelloWorld failed with about the same error on master. ResponseCompression_AppAndHostCompression failed with about the same error on master. HelloWorld failed with about the same error on master. ResponseCompression_NoCompression failed with about the same error on master. HelloWorld failed with about the same error on master. HelloWorld failed with about the same error on master. ResponseCompression_NoCompression failed with about the same error on master. HelloWorld failed with about the same error on master. ResponseCompression_AppAndHostCompression failed with about the same error on master. ResponseCompression_AppAndHostCompression failed with about the same error on master. ResponseCompression_AppCompression failed with about the same error on master. ResponseCompression_AppAndHostCompression failed with about the same error on master. HelloWorld failed with about the same error on master. ResponseCompression_AppAndHostCompression failed with about the same error on master.
This comment was made automatically. If there is a problem contact ryanbrandenburg. There were 7 failures with about the same error on master: HelloWorld ResponseCompression_NoCompression ResponseCompression_AppAndHostCompression
Same issue as elsewhere:
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)
| [0.666s] Microsoft.AspNetCore.Server.IntegrationTesting.SelfHostDeployer Information: C:\BuildAgent\work\33bdfc1cae7b2a38\modules\ServerTests\test\ServerComparison.TestSites\bin\Release\net461\ServerComparison.TestSites.exe stdout: File name: 'System.Runtime.CompilerServices.Unsafe, Version=4.0.4.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
There were 7 failures with about the same error on master:
This comment was made automatically. If there is a problem contact ryanbrandenburg. There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
This comment was made automatically. If there is a problem contact ryanbrandenburg. There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
Looks like this is ongoing. @Eilon @mkArtakMSFT is there someone who can look into Wes' recommendation here: https://github.com/aspnet/Home/issues/3544#issuecomment-423692971?
There were 7 failures with about the same error on master:
This comment was made automatically. If there is a problem contact ryanbrandenburg. There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
This comment was made automatically. If there is a problem contact ryanbrandenburg. There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
This comment was made automatically. If there is a problem contact ryanbrandenburg. There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
There were 7 failures with about the same error on master:
This was solved when @natemcmaster fixes aspnet/Home#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 @Eilon (because the bot doesn't know who else to pick)
This issue was made automatically. If there is a problem contact ryanbrandenburg.