From: Cleber Rosa <cr...@redhat.com>
When running on very low powered environments, some tests may time out
causing false negatives. As a conservative change, and for
considering that human time (investigating false negatives) is worth
more than some extra machine cycles (and time), let's increase the
overall timeout.
CC: Alex Bennée <alex.ben...@linaro.org>
Signed-off-by: Cleber Rosa <cr...@redhat.com>
Reviewed-by: Cornelia Huck <coh...@redhat.com>
Message-Id: <20190312171824.5134-11-cr...@redhat.com>
Signed-off-by: Eduardo Habkost <ehabk...@redhat.com>
---
tests/acceptance/boot_linux_console.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/acceptance/boot_linux_console.py
b/tests/acceptance/boot_linux_console.py
index a94f5cd2c8..bfcae3771b 100644
--- a/tests/acceptance/boot_linux_console.py
+++ b/tests/acceptance/boot_linux_console.py
@@ -19,7 +19,7 @@ class BootLinuxConsole(Test):
kernel command line is properly passed from QEMU to the kernel
"""
- timeout = 60
+ timeout = 90
KERNEL_COMMON_COMMAND_LINE = 'printk.time=0 '
--
2.18.0.rc1.1.g3f1ff2140
