-
-
Notifications
You must be signed in to change notification settings - Fork 479
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
[Bug]: Fail-fast of wait.LogStrategy doesn't work properly #1302
Labels
bug
An issue with the library
Comments
Regarding the test case provided in the issue, it's wrong in the sense that it's not honouring the desired state of the container. In that sense not only the log strategy but all of them should detect that state the soonest. I did check that (see #1304 (comment)) and we do it everywhere else but in the log strategy. Please see my comment for a plausible and different fix |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Testcontainers version
0.21.0
Using the latest Testcontainers version?
Yes
Host OS
Linux (WSL2)
Host arch
x86
Go version
1.20.5
Docker version
Client: Docker Engine - Community Cloud integration: v1.0.33 Version: 24.0.2 API version: 1.43 Go version: go1.20.4 Git commit: cb74dfc Built: Thu May 25 21:52:17 2023 OS/Arch: linux/amd64 Context: default Server: Docker Desktop Engine: Version: 24.0.2 API version: 1.43 (minimum version 1.12) Go version: go1.20.4 Git commit: 659604f Built: Thu May 25 21:52:17 2023 OS/Arch: linux/amd64 Experimental: true containerd: Version: 1.6.21 GitCommit: 3dce8eb055cbb6872793272b4f20ed16117344f8 runc: Version: 1.1.7 GitCommit: v1.1.7-0-g860f061 docker-init: Version: 0.19.0 GitCommit: de40ad0
Docker info
What happened?
In the following code, mysql container immediately stops due to missing environment variables.
In this case, LogStrategy should detect the container stop and immediately return an error(#944).
However, it keeps waiting until timeout actually.
Relevant log output
Additional information
The text was updated successfully, but these errors were encountered: