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.
@mkArtakMSFT can you assign?
@mkArtakMSFT - ping
@javiercn, can you please look into this and see whether this is still an issue or not? Thanks!
Just looked at it. It was a transient network error as this test needs to go and download an external resource to hash it and validate our integrity tags.
We could add a retry here if we have to, but I would do nothing for now until it manifests itself again (if ever)
This will almost certainly fail again if it uses external network. I recommend adding a retry sooner rather than later (but perhaps not critically urgent).
@javiercn , please either add retries or whatever is necessary to reduce the chance of happening this again.
Yes, I will do so once I handle other build issues
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.