Podman: 050-stop.bats: FAIL: podman stop: took too long
Snippet of test failure
# https://s3.us-east-1.amazonaws.com/arr-cki-prod-datawarehouse-public/datawarehouse-public/2022/07/27/redhat:598411511/build_x86_64_redhat:598411511_x86_64/tests/3/results_0001/job.02/recipes/12354628/tasks/2/logs/050-stop.log
[2022-07-28 04:07:35] 050-stop.bats
[04:07:35] START - All [+xxxx] lines that follow are relative to 2022-07-28T04:07:35.
[+0001s] 1..7
[+0016s] ok 1 podman stop - basic test
[+0026s] ok 2 podman stop --all
[+0028s] ok 3 podman stop --ignore
[+0038s] not ok 4 podman stop - can trap signal
[+0038s] # (from function `assert' in file /usr/share/podman/test/system/helpers.bash, line 598,
[+0038s] # in test file /usr/share/podman/test/system/050-stop.bats, line 104)
[+0038s] # `assert $delta_t -le 2 "podman stop: took too long"' failed
[+0038s] # # podman rm -t 0 --all --force --ignore
[+0038s] # # podman ps --all --external --format {{.ID}} {{.Names}}
[+0038s] # # podman images --all --format {{.Repository}}:{{.Tag}} {{.ID}}
[+0038s] # quay.io/libpod/testimage:20210610 9f9ec7f2fdef
[+0038s] # # podman run -d quay.io/libpod/testimage:20210610 sh -c trap 'echo Received SIGTERM, finishing; exit' SIGTERM; echo READY; while :; do sleep 1; done
[+0038s] # 34a8e2b4a823e22e5c0e2205ef1efe9f43adb6e5007d566f44f2a8beec6864a8
[+0038s] # # podman logs 34a8e2b4a823e22e5c0e2205ef1efe9f43adb6e5007d566f44f2a8beec6864a8
[+0038s] # READY
[+0038s] # # podman stop 34a8e2b4a823e22e5c0e2205ef1efe9f43adb6e5007d566f44f2a8beec6864a8
[+0038s] # 34a8e2b4a823e22e5c0e2205ef1efe9f43adb6e5007d566f44f2a8beec6864a8
[+0038s] # # podman logs 34a8e2b4a823e22e5c0e2205ef1efe9f43adb6e5007d566f44f2a8beec6864a8
[+0038s] # READY
[+0038s] # Received SIGTERM, finishing
[+0038s] # # podman inspect --format {{.State.ExitCode}} 34a8e2b4a823e22e5c0e2205ef1efe9f43adb6e5007d566f44f2a8beec6864a8
[+0038s] # 0
[+0038s] # # podman rm 34a8e2b4a823e22e5c0e2205ef1efe9f43adb6e5007d566f44f2a8beec6864a8
[+0038s] # 34a8e2b4a823e22e5c0e2205ef1efe9f43adb6e5007d566f44f2a8beec6864a8
[+0038s] # # podman run -d quay.io/libpod/testimage:20210610 sh -c trap 'echo Received SIGTERM, finishing; exit' SIGTERM; echo READY; while :; do sleep 1; done
[+0038s] # a28a9312ac887bd6bf33fbeb9ab061fbb32fe043edbc510a8b7a4879260e6770
[+0038s] # # podman logs a28a9312ac887bd6bf33fbeb9ab061fbb32fe043edbc510a8b7a4879260e6770
[+0038s] # READY
[+0038s] # # podman stop --time=5 a28a9312ac887bd6bf33fbeb9ab061fbb32fe043edbc510a8b7a4879260e6770
[+0038s] # a28a9312ac887bd6bf33fbeb9ab061fbb32fe043edbc510a8b7a4879260e6770
[+0038s] # # podman logs a28a9312ac887bd6bf33fbeb9ab061fbb32fe043edbc510a8b7a4879260e6770
[+0038s] # READY
[+0038s] # Received SIGTERM, finishing
[+0038s] # # podman inspect --format {{.State.ExitCode}} a28a9312ac887bd6bf33fbeb9ab061fbb32fe043edbc510a8b7a4879260e6770
[+0038s] # 0
[+0038s] # #/vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
[+0038s] # #| FAIL: podman stop: took too long
[+0038s] # #| expected: -le '2'
[+0038s] # #| actual: '3'
[+0038s] # #\^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[+0038s] # # [teardown]
[+0038s] # # podman pod rm -t 0 --all --force --ignore
[+0038s] # # podman rm -t 0 --all --force --ignore
[+0038s] # a28a9312ac887bd6bf33fbeb9ab061fbb32fe043edbc510a8b7a4879260e6770
[+0038s] # # podman network prune --force
[+0044s] ok 5 podman stop - unlock while waiting for timeout
[+0049s] ok 6 podman stop -t 1 Generate warning
[+0052s] ok 7 podman stop --noout
[04:08:27] END - [+0052s] total duration since 2022-07-28T04:08:27
Test logs on DataWarehouse
DataWarehouse issue
-
DW issue : https://datawarehouse.cki-project.org/issue/1448
-
Regex
: https://datawarehouse.cki-project.org/issue/-/regex/1415- Text Match :
#\/v+\s*\[\+\d+s\] # #\|\s+FAIL: podman stop: took too long\s*\[\+\d+s\] # #\| expected: -le '\d+'\s*\[\+\d+s\] # #\|\s+actual:\s+'\d+'
- (Log) File Name Match :
taskout\.log
- Test Name Match :
Podman.*
- KPET Tree Name Match :
(upstream|rawhide|eln)
- Text Match :
-
Additional details
N/A
In case opening the links above result in a 404 page on DataWarehouse, please make sure you are correctly logged into DataWarehouse via Red Hat SSO.