From bdb3f91eb4c0a619682049b2ffa5a3cf252d2133 Mon Sep 17 00:00:00 2001 From: Milas Bowman Date: Thu, 3 Aug 2023 14:49:59 -0400 Subject: [PATCH] test: temporarily disable an exit-code-from Cucumber test case (#10875) Something is wrong here, disabling while we investigate. Signed-off-by: Milas Bowman --- e2e/cucumber-features/stop.feature | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-) diff --git a/e2e/cucumber-features/stop.feature b/e2e/cucumber-features/stop.feature index 9f6b0d93..2fc0a273 100644 --- a/e2e/cucumber-features/stop.feature +++ b/e2e/cucumber-features/stop.feature @@ -6,7 +6,7 @@ Background: services: should_fail: image: alpine - command: ls /does_not_exist + command: ['sh', '-c', 'exit 123'] sleep: # will be killed image: alpine command: ping localhost @@ -15,15 +15,22 @@ Background: Scenario: Cascade stop When I run "compose up --abort-on-container-exit" - Then the output contains "should_fail-1 exited with code 1" + Then the output contains "should_fail-1 exited with code 123" And the output contains "Aborting on container exit..." - And the exit code is 1 + And the exit code is 123 Scenario: Exit code from - When I run "compose up --exit-code-from sleep" - Then the output contains "should_fail-1 exited with code 1" + When I run "compose up --exit-code-from should_fail" + Then the output contains "should_fail-1 exited with code 123" And the output contains "Aborting on container exit..." - And the exit code is 143 + And the exit code is 123 + +# TODO: this is currently not working propagating the exit code properly +#Scenario: Exit code from (cascade stop) +# When I run "compose up --exit-code-from sleep" +# Then the output contains "should_fail-1 exited with code 123" +# And the output contains "Aborting on container exit..." +# And the exit code is 143 Scenario: Exit code from unknown service When I run "compose up --exit-code-from unknown"