Closed ash2k closed 5 days ago
Name | Link |
---|---|
Latest commit | 9d6ff022a3e926b588ad17b5a1536388efa4bd52 |
Latest deploy log | https://app.netlify.com/sites/testcontainers-go/deploys/667cd99ddac08f00081f4e17 |
Deploy Preview | https://deploy-preview-2608--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.
The tests failing for the rootless mode are not related. Merging
What does this PR do?
I was debugging failures in CI and found a few issues in code. See individual commits. I think the failure was not a real log reading failure - the container just failed to start for an unexpected reason but the test didn't catch it because it didn't check the error message.
Then, panic is a red herring too because the returned container is
nil
.Why is it important?
We want clear test signals that help pinpoint the bugs, we don't want hard to understand failures.
Related issues