From 345418a9e67a5f5f86901b2e1f86f52526ca7ba1 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Wed, 6 Apr 2022 11:57:13 +0200 Subject: [PATCH] test-loop-block: reenable test on CI --- src/test/test-loop-block.c | 6 ------ 1 file changed, 6 deletions(-) diff --git a/src/test/test-loop-block.c b/src/test/test-loop-block.c index 2f3c3745e2..714d51cfc2 100644 --- a/src/test/test-loop-block.c +++ b/src/test/test-loop-block.c @@ -158,12 +158,6 @@ static int run(int argc, char *argv[]) { return EXIT_TEST_SKIP; } - if (strstr_ptr(ci_environment(), "autopkgtest") || strstr_ptr(ci_environment(), "github-actions")) { - // FIXME: we should reenable this one day - log_tests_skipped("Skipping test on Ubuntu autopkgtest CI/GH Actions, test too slow and installed udev too flakey."); - return EXIT_TEST_SKIP; - } - /* This is a test for the loopback block device setup code and it's use by the image dissection * logic: since the kernel APIs are hard use and prone to races, let's test this in a heavy duty * test: we open a bunch of threads and repeatedly allocate and deallocate loopback block devices in