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.
ResponseCompression_AppAndHostCompression failed with about the same error on 2.2.
This comment was made automatically. If there is a problem contact ryanbrandenburg.
@muratg can you assign?
@Tratcher could you take an initial look please?
Hmm, it's still having port conflicts bind() to 0.0.0.0:40912 failed (98: Address already in use)
HelloWorld failed with about the same error on master.
This comment was made automatically. If there is a problem contact ryanbrandenburg.
This most recent failure is unrelated, there's a bad corefx in play. https://github.com/aspnet/Home/issues/3544
There were 1 failures with about the same error on 2.2:
This comment was made automatically. If there is a problem contact ryanbrandenburg.
This comment was made automatically. If there is a problem contact ryanbrandenburg.
There were 1 failures with about the same error on master at 10:55:30 AM:
There were 1 failures with about the same error on master at 1:21:35 PM:
This comment was made automatically. If there is a problem contact ryanbrandenburg.
There were 1 failures with about the same error on 2.1 at 4:33:46 PM:
There were 1 failures with about the same error on 2.1 at 1:36:28 AM:
This comment was made automatically. If there is a problem contact ryanbrandenburg.
There were 1 failures with about the same error on 2.1 at 4:47:15 PM:
There were 1 failures with about the same error on master at 6:40:36 PM:
This comment was made automatically. If there is a problem contact ryanbrandenburg.
There were 1 failures with about the same error on 2.2 at 12:10:10 PM:
This comment was made automatically. If there is a problem contact ryanbrandenburg.
There were 1 failures with about the same error on master at 7:03:30 PM:
More [emerg] bind() to 0.0.0.0:37971 failed (98: Address already in use)
failures, all branches.
Closing this. We've improved the test logging so we'll see what we get if this happens again.
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 2.1.
CC @Eilon (because the bot doesn't know who else to pick)
This issue was made automatically. If there is a problem contact ryanbrandenburg.