-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DNS still flaky on windows #2086
Comments
After some attempts by both @Arqu and I a few weeks ago, we were both unable to trigger the DNS test failure. I also checked: since this issue was created (which is, I'm assuming the same time that this test was flakey on CI) it hasn't failed on a single "Flakey: CI" run. So, when do we decide that this isn't really a flakey test, and that your previous work on DNS actually fixed the issue? |
if there isn't a single flaky instance of this let's move it back to not flaky. if it turns out flaky again it'll be moved back to the sin bin swiftly enough |
## Description They have been stable on CI for a while now. Maybe the DNS config tweak we did in #2075 made a difference. ## Breaking Changes <!-- Optional, if there are any breaking changes document them, including how to migrate older code. --> ## Notes & open questions Closes #2086 ## Change checklist - [x] Self-review. - ~~[ ] Documentation updates if relevant.~~ - ~~[ ] Tests if relevant.~~ - ~~[ ] All breaking changes documented.~~
## Description This reverts commit 93bcaa5. Re-opens #2086 ## Breaking Changes <!-- Optional, if there are any breaking changes document them, including how to migrate older code. --> ## Notes & open questions <!-- Any notes, remarks or open questions you have to make about the PR. --> ## Change checklist - [x] Self-review. - [x] Documentation updates if relevant. - [x] Tests if relevant. - [x] All breaking changes documented.
Let's try to close this again. The staggered DNS approach seems successful. |
It seems the windows CI is still giving us timeouts on DNS resolution. This is weird.
The text was updated successfully, but these errors were encountered: