-
Notifications
You must be signed in to change notification settings - Fork 117
Closed
Description
Originally opened by @teojgo and abandoned due to errors. We were simply missing an option!
./test_reframe.py --process-timeout=300 --processes=4
................................................................................SSS...S...................................................SSSSSS.......................................................S...........................................................................S..S................S.S..SS..S.S..SS.........................................................
----------------------------------------------------------------------
Ran 368 tests in 18.155s
OK (SKIP=21)
vs single-threaded:
....S........................................................SSS...S...................................................................................................SSSSSS..............................S..S.........................................................................................................................S.S..SS..S.S..SS.......................
----------------------------------------------------------------------
Ran 368 tests in 47.144s
OK (SKIP=21)
The only thing is what is a reasonable timeout? I would say to put set it to quite a high number, since for the submission unit tests, we might get stuck in the job scheduler for a long time if the target system is too loaded.
Internal issue: https://madra.cscs.ch/scs/reframe/issues/521