-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Flaky http tests tyrian.HttpTests
#199
Comments
tyrian.HttpTests
tyrian.HttpTests
Annoyingly I can't replicate this now. Will leave the issue open a bit longer... |
Seems like the tests I added 😞 I wonder if httpbin was having issues at the time? That's the downside of depending on an external service for the unit tests... |
Yeah it's being flaky again this morning - no worries though, it's still a massive improvement to have tests for this stuff! I think maybe I'll just have to switch httpbin out for some sort of mock when I get a chance. |
I've disable the tests for now and left the following comment in the code while I have a think about what to do next:
I do want to bring them back though! Just not quite sure how best to proceed. httpbin is available as a Docker image, but I really dislike docker. 😋 |
Understandable, I also thought about some sbt magic that would start the httpbin container just for the tests but I didn't like the idea and my sbt knowledge is also questionable. I think @armanbilge had some fancy setup in their project with some simple http4s server running only for the tests or something? Maybe we can make an http4sbin 😅 |
The thought crossed my mind... 😄 |
httpbin is actually a python program, so its available like that as well. |
I happened to be manually testing an http call to httpbin this morning and it was a bit slow. I wonder if we could get away with just having retries with a backoff policy... |
Were you thinking of adding the retry policy to the API itself or just for the tests? |
They are pretty slow and fail intermittently. Here for example the HEAD test passed, but I've seen it fail too, despite no code changes in that area.
The text was updated successfully, but these errors were encountered: