Closed aspnet-hello closed 5 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.
AnonymousUserCantAccessAuthorizedPages failed with about the same error on 2.2.
This comment was made automatically. If there is a problem contact ryanbrandenburg.
@mkArtakMSFT - please assign.
QueryingIdentityEndpointsReturnsNotFoundWhenIdentityIsNotPresent failed with about the same error on 2.2.
This comment was made automatically. If there is a problem contact ryanbrandenburg.
@mkArtakMSFT was this resolved? If so how? Please assign someone to find out.
@javiercn ? @pranavkm ?
@Eilon Sounds like an MSBuild issue/race condition?
We haven't seen this on MVC and it's not a problem customers have reported.
Can we dig into that a bit more? Are we assuming determinism of MSBuild when perhaps that is an invalid assumption? Can we get in touch with those folks to try to understand this better?
Could we close this? No reports of additional failures over 2 weeks now.
Do you have a hypothesis on why this might have started passing again?
@ryanbrandenburg I think this has been a transient issue. Our stack is so complex that I wouldn't even know where to start in order to look into this. I'm confident that this is not something we have caused as we haven't changed this code in months, so I will agree with @pranavkm in that we should close this.
The only thing we can do is to enable binary logs in all our builds so that we can do postmortems on these things, but without that, it's impossible to troubleshoot.
I don't see this issue anymore, in any build for the past month, so closing.
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.2.
CC @Eilon (because the bot doesn't know who else to pick)
This issue was made automatically. If there is a problem contact ryanbrandenburg.