From f8eba38801a853ed2f8b1635bcda35139ae86815 Mon Sep 17 00:00:00 2001 From: Eli Schwartz Date: Thu, 9 Mar 2023 22:56:17 -0500 Subject: [PATCH] tests: allow a long test to have more time to complete before timing out This test is intended to test really long output, so it prints 100k lines of stdout/stderr. It completes in two seconds on my machine, but the default 30-second timeout is apparently too much for CI, because on Windows we often get flaky tests due to this. e.g. we'll get within 200 lines of the end. Bump the CI time by x2. We know this isn't particularly surprising behavior, and allowing it to request another 30 seconds won't hang the CI. But it will save us from some spurious failures and restarted jobs. --- test cases/common/254 long output/meson.build | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/test cases/common/254 long output/meson.build b/test cases/common/254 long output/meson.build index 6d8d62b22..145dcb478 100644 --- a/test cases/common/254 long output/meson.build +++ b/test cases/common/254 long output/meson.build @@ -1,5 +1,5 @@ project('long-stderr', 'c') dumper = executable('dumper', 'dumper.c') -test('dump-test', dumper) -test('dump-test-TAP', dumper, protocol : 'tap') +test('dump-test', dumper, timeout: 60) +test('dump-test-TAP', dumper, protocol : 'tap', timeout: 60)