Closed aspnet-hello closed 5 years ago
This comment was made automatically. If there is a problem contact ryanbrandenburg.
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.
There were 1 failures with about the same error on 2.2 at 10:17:09 AM:
There were 2 failures with about the same error on master at 12:14:23 PM:
There were 2 failures with about the same error on master at 12:19:57 PM:
There were 2 failures with about the same error on master at 11:39:34 AM:
There were 2 failures with about the same error on master at 1:25:59 PM:
There were 2 failures with about the same error on master at 11:51:38 AM:
There were 2 failures with about the same error on master at 11:50:13 AM:
There were 2 failures with about the same error on master at 11:57:00 AM:
There were 2 failures with about the same error on master at 1:40:25 PM:
There were 2 failures with about the same error on master at 2:10:40 PM:
@Tratcher can you take a look?
We need to react to https://github.com/aspnet/Universe/commit/06e9531d50f80d834decdf2a6696df4618bfcba5, or at least make the test less strict about these fields.
@HaoK FYI
This comment was made automatically. If there is a problem contact ryanbrandenburg.
There were 2 failures with about the same error on master at 2:33:08 PM:
There were 2 failures with about the same error on master at 2:33:07 PM:
There were 2 failures with about the same error on master at 2:31:34 PM:
There were 2 failures with about the same error on master at 2:45:17 PM:
There were 2 failures with about the same error on master at 11:19:38 PM:
There were 2 failures with about the same error on master at 11:15:24 PM:
There were 2 failures with about the same error on master at 11:15:23 PM:
There were 2 failures with about the same error on master at 11:15:17 PM:
There were 2 failures with about the same error on master at 11:15:24 PM:
There were 2 failures with about the same error on master at 11:15:24 PM:
There were 2 failures with about the same error on master at 11:15:24 PM:
There were 2 failures with about the same error on master at 1:07:41 AM:
There were 2 failures with about the same error on 2.2 at 11:24:35 AM:
@Tratcher does your fix address the 2 more recent failures?
Oh sorry just realized they're the same. So hopefully yes 😄
This issue was made automatically. If there is a problem contact ryanbrandenburg.
This test failed 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.2.
CC @Eilon (because the bot doesn't know who else to pick)