tyler.durden/compose
1
0
Fork 0
mirror of https://github.com/docker/compose.git synced 2025-07-27 07:34:10 +02:00
Code Issues Packages Projects Releases Wiki Activity

test: speed up Cucumber stop test (#10032)

Browse Source 
Evidently `ping` doesn't respond to `SIGTERM`, so use `init` to
get Tini supervising it. This changes the exit code to 143 since
it's not hitting the 10s timeout and getting a `SIGKILL` (137).

Signed-off-by: Milas Bowman <milas.bowman@docker.com>
This commit is contained in:
Milas Bowman 2022-12-02 09:34:06 -05:00 committed by GitHub
parent c74a77e895
commit b9e5f9e917
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
e2e/cucumber-features/stop.feature
View File

@ -10,6 +10,7 @@ Background:
sleep: # will be killed sleep: # will be killed
image: alpine image: alpine
command: ping localhost command: ping localhost
init: true
""" """
Scenario: Cascade stop Scenario: Cascade stop
@ -22,7 +23,7 @@ Scenario: Exit code from
When I run "compose up --exit-code-from sleep" When I run "compose up --exit-code-from sleep"
Then the output contains "should_fail-1 exited with code 1" Then the output contains "should_fail-1 exited with code 1"
And the output contains "Aborting on container exit..." And the output contains "Aborting on container exit..."
And the exit code is 137 And the exit code is 143
Scenario: Exit code from unknown service Scenario: Exit code from unknown service
When I run "compose up --exit-code-from unknown" When I run "compose up --exit-code-from unknown"