Closed ash2k closed 2 months ago
Name | Link |
---|---|
Latest commit | f5adf1dbb59bcaf3ecb21ef2a93a7caba3c5de7c |
Latest deploy log | https://app.netlify.com/sites/testcontainers-go/deploys/6686b8ff23116800080bca44 |
Deploy Preview | https://deploy-preview-2613--testcontainers-go.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Could you please update this PR with the changes in #2606 🙏
Thanks!
Rebased
Tests are failing with:
2024/07/02 23:11:31 Failed to pull image: Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit, will retry
Rebased
I'm sorry but I do not see the changes for the lifecycle.go function, adding a retry for checking all exposed ports are already available.
Hm, I've just checked and I think all commits are there:
main
branch of this repo: https://github.com/testcontainers/testcontainers-go/commits/main/Am I missing something?
Oh sorry, I probably did not explain myself very well. I asked you to check (and update if neeeded) the retry added in #2606, to include the RetryNotify pattern this PR introduces 🙏
Ah, ok. Done!
What does this PR do?
Add logging of errors that are retried.
Why is it important?
I want to see any unexpected errors when they happen. Otherwise nothing is logged and the test appears to be stuck forever.
Related issues