-
Notifications
You must be signed in to change notification settings - Fork 67
Possibly add retry to async tests #742
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
Comments
These are the local integration tests? Could you post one of the failure messages next time you hit this? |
Yup! Here are some error messages:
and
This is what the docker web-server log shows when it occurs
|
does this still happen? i cant remember the last time i saw this (though absence of evidence is not evidence of absence, and my memory can be faulty)... changes elsewhere in the server code may have resolved the issue, and im pushing to deprecate the async stuff, so this can probably be closed. |
When I was working on JIT last Winter, I don't recall running into this. Maybe it got fixed, maybe not, but agree that there's little reason to hunt for ghost bugs in code that's planned to deprecate. |
Some of the async tests sporadically fail, due to a suspected race condition, but fail after a few more retries of the tests. We may want to add a retry condition to automatically do this.
The text was updated successfully, but these errors were encountered: