libregrtest from 3.14.2 by youknowone · Pull Request #6818 · RustPython/RustPython
-S is used to continue running tests after an aborted run. It will maintain the order a standard run (ie, this assumes -r is not used). -S is used to resume running tests after an interrupted run. It will maintain the order a standard run (i.e. it assumes -r is not used). This is useful after the tests have prematurely stopped for some external reason and you want to start running from where you left off rather than starting from the beginning. reason and you want to resume the run from where you left off rather than starting from the beginning. Note: this is different from --prioritize.
--prioritize is used to influence the order of selected tests, such that the tests listed as an argument are executed first. This is especially useful when combined with -j and -r to pin the longest-running tests to start at the beginning of a test run. Pass --prioritize=test_a,test_b to make test_a run first, followed by test_b, and then the other tests. If test_a wasn't selected for execution by regular means, --prioritize will not make it execute.
-f reads the names of tests from the file given as f's argument, one or more test names per line. Whitespace is ignored. Blank lines and
all - Enable all special resources. all - Enable all special resources.
none - Disable all special resources (this is the default).
none - Disable all special resources (this is the default). audio - Tests that use the audio device. (There are known cases of broken audio drivers that can crash Python or even the Linux kernel.)
audio - Tests that use the audio device. (There are known cases of broken audio drivers that can crash Python or even the Linux kernel.) curses - Tests that use curses and will modify the terminal's state and output modes.
curses - Tests that use curses and will modify the terminal's state and output modes. largefile - It is okay to run some test that may create huge files. These tests can take a long time and may consume >2 GiB of disk space temporarily.
largefile - It is okay to run some test that may create huge files. These tests can take a long time and may consume >2 GiB of disk space temporarily. extralargefile - Like 'largefile', but even larger (and slower).
network - It is okay to run tests that use external network resource, e.g. testing SSL support for sockets. network - It is okay to run tests that use external network resource, e.g. testing SSL support for sockets.
decimal - Test the decimal module against a large suite that verifies compliance with standards. decimal - Test the decimal module against a large suite that verifies compliance with standards.
cpu - Used for certain CPU-heavy tests. cpu - Used for certain CPU-heavy tests.
walltime - Long running but not CPU-bound tests. walltime - Long running but not CPU-bound tests.
subprocess Run all tests for the subprocess module. subprocess Run all tests for the subprocess module.
urlfetch - It is okay to download files required on testing. urlfetch - It is okay to download files required on testing.
gui - Run tests that require a running GUI. gui - Run tests that require a running GUI.
tzdata - Run tests that require timezone data. tzdata - Run tests that require timezone data.
To enable all resources except one, use '-uall,-<resource>'. For example, to run all the tests except for the gui tests, give the
def priority_list(string): return string.split(",")
def _parse_args(args, **kwargs): # Defaults ns = Namespace()
ns.prioritize = [ test for test_list in (ns.prioritize or ()) for test in test_list ]
return ns