diff options
| author | Ed Santiago <santiago@redhat.com> | 2020-08-13 14:55:10 -0600 |
|---|---|---|
| committer | Ed Santiago <santiago@redhat.com> | 2020-08-13 19:16:25 -0600 |
| commit | 60ab5f3ae66e04be83ec4f83ad4b29b6e294110c (patch) | |
| tree | e9cb4bfb904a2ee3c79da25ba7e71e45bc75db71 /Vagrantfile | |
| parent | 81499a5c470797221abca6facbfe27ccf7c6cbdb (diff) | |
| download | podman-60ab5f3ae66e04be83ec4f83ad4b29b6e294110c.tar.gz podman-60ab5f3ae66e04be83ec4f83ad4b29b6e294110c.tar.bz2 podman-60ab5f3ae66e04be83ec4f83ad4b29b6e294110c.zip | |
system tests: enable sdnotify tests
Oops. PR #6693 (sdnotify) added tests, but they were disabled
due to broken crun on f31. I tried for three weeks to get a
magic CI:IMG PR to update crun on the CI VMs ... but in that
time I forgot to actually enable those new tests.
This PR removes a 'skip', replacing it with a check that systemd
is running plus one more to make sure our runtime is crun. It
looks like sdnotify just doesn't work on Ubuntu (it hangs), and
my guess is that it's a crun/runc issue.
I also changed the test image from fedora:latest to :31, because,
sigh, fedora:latest removed the systemd-notify tool.
WARNING WARNING WARNING: the symptom of a missing systemd-notify
is that podman will hang forever, not even stopped by the timeout
command in podman_run! (Filed: #7316). This means that if the
sdnotify-in-container test ever fails, the symptom will be that
Cirrus itself will time out (2 hours?). This is horrible. I
don't know what to do about it other than push for a fix for 7316.
Signed-off-by: Ed Santiago <santiago@redhat.com>
Diffstat (limited to 'Vagrantfile')
0 files changed, 0 insertions, 0 deletions