summaryrefslogtreecommitdiff
path: root/test/system/260-sdnotify.bats
diff options
context:
space:
mode:
authorEd Santiago <santiago@redhat.com>2020-08-18 07:21:47 -0600
committerEd Santiago <santiago@redhat.com>2020-08-18 07:21:47 -0600
commit18f36d8cf6bd1fa4681035dcb38af1bd61789a5c (patch)
treeb79cf74377e57c55d2ad481c709ecd5637d08e8f /test/system/260-sdnotify.bats
parent49d6468b939a3c4ffed4d529c438f3849c252e7b (diff)
downloadpodman-18f36d8cf6bd1fa4681035dcb38af1bd61789a5c.tar.gz
podman-18f36d8cf6bd1fa4681035dcb38af1bd61789a5c.tar.bz2
podman-18f36d8cf6bd1fa4681035dcb38af1bd61789a5c.zip
Re-disable sdnotify tests to try to fix CI
Some CI tests are hanging, timing out in 60 or 120 minutes. I wonder if it's #7316, the bug where all podman commands hang forever if NOTIFY_SOCKET is set? Signed-off-by: Ed Santiago <santiago@redhat.com>
Diffstat (limited to 'test/system/260-sdnotify.bats')
-rw-r--r--test/system/260-sdnotify.bats2
1 files changed, 2 insertions, 0 deletions
diff --git a/test/system/260-sdnotify.bats b/test/system/260-sdnotify.bats
index 6bc9fc02e..7be4be983 100644
--- a/test/system/260-sdnotify.bats
+++ b/test/system/260-sdnotify.bats
@@ -12,6 +12,8 @@ _SOCAT_LOG=
function setup() {
skip_if_remote
+ skip "FIXME FIXME FIXME, is this what's causing the CI hang???"
+
# Skip if systemd is not running
systemctl list-units &>/dev/null || skip "systemd not available"