Add a new parameter jobs to the runRegressiontest function. By
default this is set to 0. This will be passed to the test.py script
which will use it to determine the number of jobs to use for running
tests.
If tests jobs are done one at a time, i.e. --jobs=1 is set for the
python test script, assume that we are allowed to use multiple threads
for each test itself. That is, allow omcto run single tests with its
own multiple threads when needed.
This should ideally be its own flag/option passed to the test script.
However, with the current requirements it is an overkill.
Trim whitespace.
Rename function for clarity.
test()torunRegressionTest().testis too generic and difficult to notice.Rename option to 'j' instead of 'n'.
-nis used by OpenModelica itself to control its own number of threads.-j (--jobs)for the python script instead to avoid confusion.Allow specifying the number of jobs for regression testing.
jobsto therunRegressiontestfunction. By default this is set to 0. This will be passed to thetest.pyscript which will use it to determine the number of jobs to use for running tests.If running on test at a time allow
omcmultithreading.If tests jobs are done one at a time, i.e.
--jobs=1is set for the python test script, assume that we are allowed to use multiple threads for each test itself. That is, allowomcto run single tests with its own multiple threads when needed.This should ideally be its own flag/option passed to the test script. However, with the current requirements it is an overkill.
Add a new job 'heavy_tests'.
This job will run test one at a time. That is, it will not launch multiple tests at once.
However, for each individual test,
omcshould be allowed to use multiple threads (e.g. to load libraries, generate and compile C code).The job is intended to be manually started (no schedule for now).
The name of the job is preliminary and can be changed.