Skip to content

Conversation

mokibit
Copy link
Collaborator

@mokibit mokibit commented Jul 2, 2025

Currently, the failure exit code from the push command is not forwarded as the exit code for podman-compose.
With this PR, failure exit code is correctly forwarded when the underlying podman command fails.

This PR completes PR #521, dealing with the push and run commands as the same problem with build command was resolved by PR #1168.
The run command already correctly forwards failure exit codes, so only a test was added for it.

mokibit added 2 commits July 2, 2025 23:34
Failure exit code for `push` command is not currently forwarded as exit
code for podman-compose.
With this PR, podman-compose stops pushing when the underlying podman
command fails and forwards its exit code.

Signed-off-by: Monika Kairaityte <monika@kibit.lt>
Test is added to confirm that `run` command forwards non-zero failure
exit code.

Signed-off-by: Monika Kairaityte <monika@kibit.lt>
@mokibit mokibit force-pushed the push-non-zero-exit-code branch 3 times, most recently from 09bf7ce to ed1159d Compare July 2, 2025 20:50
Renamed directory `build_fail_multi` to more appropriate
`commands_fail_exit_code` as more tests were added to other
commands:`push` and `run`. Names of tests were changed accordingly.

Signed-off-by: Monika Kairaityte <monika@kibit.lt>
@mokibit mokibit force-pushed the push-non-zero-exit-code branch from ed1159d to b3fd550 Compare July 3, 2025 11:38
@p12tic p12tic merged commit 406596e into containers:main Jul 3, 2025
8 checks passed
@p12tic p12tic mentioned this pull request Jul 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants