Closed ryanbrandenburg 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.
IdentityUI_ScriptTags_SubresourceIntegrityCheck failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
@javiercn - please take a look at this high priority flaky test issue.
@kichalla As I believe he wrote these tests :)
IdentityUI_ScriptTags_SubresourceIntegrityCheck failed again.
'failed again' seems incorrect here...both the OP and the new comment point to the same build..
Not a flaky test actually. Looking at test history, it has been very stable. The failure mentioned in this bug is a one off thing I would say. We could add retry logic as a general good practice, but I wouldn't consider it as a high priority.
What does "one off" mean? Can it not fail again in the same way? Was there a bug that was fixed?
This test failed because it was unable to reach ajax.aspnetcdn.com
. Sure, there's a possibility that it could fail again for similar reasons. I was thinking of adding a retry logic to these tests, but was thinking that could be done at a lower priority considering the test's history. (Even if we add retry logic, its still not fail proof though). No, there was no bug that was fixed.
Ah OK then we can keep this closed because we were having general network issues at around that time.
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.
CC @Eilon,@muratg,@mkArtakMSFT
This issue was made automatically. If there is a problem contact @ryanbrandenburg.