do not run scipy easyblock tests for runtest = False - #4200
Conversation
|
Test report by @Thyre Overview of tested easyconfigs (in order)
Build succeeded for 13 out of 13 (total: 50 mins 18 secs) (13 easyconfigs in total) |
|
@boegelbot please test @ jsc-zen3 |
|
@Thyre: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 5266688669 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot Overview of tested easyconfigs (in order)
Build succeeded for 2 out of 2 (total: 1 hour 30 mins 8 secs) (2 easyconfigs in total) |
|
Going in, thanks @Thyre! |
(created using
eb --new-pr)Currently, a set
runtest = Falsein the EasyConfig is completely ignored by the EasyBlock, causing the tests to be executed either way. On our systems, this can lead to a significant oversubscription due to user limits, depending on where the software is built (e.g. login node) and which user builds it. As a consequence, the tests are running for ages, partially into build job timeouts.At the same time, we do not want to skip tests altogether. The NumPy and SciPy test suites can be executed later on, so we prefer this approach.
As such, allow a user to explicitly disable running the tests.