-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Automated testing of supported backends? #1117
Comments
Backend integration tests proved to be very unstable on public CI systems (travis/circle) and reported a lot of false positives, so they were removed. If you find a way to test these in a more stable way, that would be great. |
I'll see what I can do |
@defnull could you elaborate on that? What kind of false positives? What kind of instability? |
Spawing a new process with a running server listening on localhost, waiting up to 10 seconds for the port to open, and then sending a single HTTP request, failed randomly. For various reasons. Either timeouts or port conflicts or other issues. I'm not exactly sure. |
Let's find out 😃 Found the code in |
Closing as #1118 is merged by now. Please re-open as needed. |
Hi!
Last time I checked support for multiple backends was broken. I did a superficial check for related tests in the repository now and didn't any, e.g. there is no test that backend
waitress
still works today. Am I missing something? Are there plans to get all backends covered by smoke tests at leasts? Are there tests that I am missing? Should I create a ticket for every backend I find broken?Thanks and best, Sebastian
The text was updated successfully, but these errors were encountered: