On 28/05/2024 02.42, Nicholas Piggin wrote:
As Fabiano points out, this test isn't flaky it just can't run under gitlab CI since runners have a very small shm size.Suggested-by: Fabiano Rosas <faro...@suse.de> Signed-off-by: Nicholas Piggin <npig...@gmail.com> --- tests/qtest/migration-test.c | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/tests/qtest/migration-test.c b/tests/qtest/migration-test.c index b7e3406471..04bf1c0092 100644 --- a/tests/qtest/migration-test.c +++ b/tests/qtest/migration-test.c @@ -706,6 +706,14 @@ static int test_migrate_start(QTestState **from, QTestState **to, g_test_skip("/dev/shm is not supported"); return -1; } + if (getenv("GITLAB_CI")) { + /* + * Gitlab runners are limited to 64MB shm size. See: + * https://lore.kernel.org/all/87ttq5fvh7....@suse.de/ + */ + g_test_skip("/dev/shm is not supported in Gitlab CI environment"); + return -1; + } }
Note that there is more than gitlab-CI: We can also run tests on Travis (well, hardly anybody beside me is still doing that) or other constraints container environments ... so it might be better to check whether enough space is available than to tie this to an environment variable (or even better change away from /dev/shm if possible like you did in your other patch - but I don't have a clue whether that's ok or not for these tests)
Thomas
