From 1ebc1fc554a5c750349bc61fa69206d6bb6572a3 Mon Sep 17 00:00:00 2001 From: Jarek Prokop Date: Thu, 4 Jul 2024 15:12:00 +0200 Subject: [PATCH] Increase timeout for tests using mock. When doing a fresh mock build (=~ no cached build root) the test can take a bit over 5 minutes. Since 5 minutes is the default timeout, bump it to 10 minutes for these tests. Since rubygem packages require little to no compilation, the builds are quite fast overall, so only 10m is reasonable for the package set tested for the rubygem-cucumber stack. This might require further adjustments as runtime of the test is also affected by network speed, available CPU power, how long the compilation/build takes, how long do the tests run, etc... --- tests/reverse_dependencies_build/main.fmf | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/tests/reverse_dependencies_build/main.fmf b/tests/reverse_dependencies_build/main.fmf index 2a74cf7..f444136 100644 --- a/tests/reverse_dependencies_build/main.fmf +++ b/tests/reverse_dependencies_build/main.fmf @@ -1,6 +1,15 @@ summary: Reverse rebuild a dependency with scratch build artifact test: ./test.sh +# When doing a fresh mock build (=~ no cached build root) the test can take +# a bit over 5 minutes. Since 5 minutes is the default timeout, bump it +# to 10 minutes for these tests. +# Since rubygem packages require little to no compilation, the builds +# are quite fast overall, so only 10m is reasonable for the package set +# tested for the rubygem-cucumber stack. +# NOTE: Caution is advised when adding other packages to this collection of tests. +duration: 10m + require+: - mock - python3-koji