mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-10-19 04:17:33 +00:00
fix remote run/start flake
Fix the flake reported in #9597 with a workaround to at least stop wasting energy until the root cause has been found and fixed. It seems that a remote run returns before the container has transitioned into the `exited` state which ultimately breaks a subsequent remote start with attach. Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
This commit is contained in:
parent
9bf0271e6d
commit
921e9ecbb3
1 changed files with 4 additions and 0 deletions
|
|
@ -91,6 +91,10 @@ ${cid[0]} d" "Sequential output from logs"
|
|||
|
||||
function _log_test_restarted() {
|
||||
run_podman run --log-driver=$1 --name logtest $IMAGE sh -c 'start=0; if test -s log; then start=`tail -n 1 log`; fi; seq `expr $start + 1` `expr $start + 10` | tee -a log'
|
||||
# FIXME: #9597
|
||||
# run/start is flaking for remote so let's wait for the container condition
|
||||
# to stop wasting energy until the root cause gets fixed.
|
||||
run_podman container wait --condition=exited logtest
|
||||
run_podman start -a logtest
|
||||
logfile=$(mktemp -p ${PODMAN_TMPDIR} logfileXXXXXXXX)
|
||||
$PODMAN $_PODMAN_TEST_OPTS logs -f logtest > $logfile
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue