mirror of
https://github.com/docker/compose.git
synced 2026-09-24 14:34:26 +00:00
waitDependency returned nil whenever its context ended, so an expired wait deadline was reported only when the 500ms poll ticker happened to win the select race and the condition check then failed on the expired context. Whether `up --wait --wait-timeout` failed or silently succeeded after the timeout was a coin toss, and the "timeout waiting for dependencies" mapping in waitDependencies was unreachable on the direct path. Return the context error when the deadline expired; a plain cancellation (Ctrl-C) is still not reported as a dependency failure. The unit test pins both sides deterministically (a deadline shorter than the first tick used to be swallowed with certainty); the e2e scenario documents the user-visible contract: `up --wait --wait-timeout` on a never-healthy service fails with "application not healthy after Xs" while the container keeps running. Part of #14074 (section C) / #14081 (lot 0). Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com> |
||
|---|---|---|
| .. | ||
| compose.yaml | ||