mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-09-30 14:19:16 +00:00
4505e2154e
The firmware tests would always time out for me. Add a correct timeout, including details on how the value was reached. Additionally allow the test harness to skip comments in settings files and report how long a given timeout was. Reviewed-by: SeongJae Park <sjpark@amazon.de> Acked-by: Scott Branden <scott.branden@broadcom.com> Signed-off-by: Kees Cook <keescook@chromium.org> Link: https://lore.kernel.org/r/20200724213640.389191-3-keescook@chromium.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
8 lines
527 B
Text
8 lines
527 B
Text
# The async firmware timeout is set to 1 second (but ends up being effectively
|
|
# 2 seconds). There are 3 test configs, each done with and without firmware
|
|
# present, each with 2 "nowait" functions tested 5 times. Expected time for a
|
|
# normal execution should be 2 * 3 * 2 * 2 * 5 = 120 seconds for those alone.
|
|
# Additionally, fw_fallback may take 5 seconds for internal timeouts in each
|
|
# of the 3 configs, so at least another 15 seconds are needed. Add another
|
|
# 10 seconds for each testing config: 120 + 15 + 30
|
|
timeout=165
|