gem5/tests/tests.py

69                         help="Don't translate test names to " \
102         followed by the test category and mode separated by
103         slashes. The test names emitted by this command can be fed
122                         help="List available test cases")
128         for test in get_tests(isa, categories=categories, modes=modes,
131             print("/".join(test))
141         Run one or more tests described by a gem5 test tuple.
143         The test tuple consists of a test category (quick or long), a
144         test mode (fs or se), a workload name, an isa, an operating
149         (e.g., "tests.py list arm/quick" or one of the scons test list
152         The test results can be stored in multiple different output
159     parser.add_argument("test", type=str, nargs="*",
190     for test_name in args.test:
201     for testno, test in enumerate(tests):
202         print("%i: Running '%s'..." % (testno, test))
204         all_results.append(test.run())
212         help='Display pickled test results',
213         description='Display pickled test results',
215         Reformat the pickled output from one or more test runs. This
216         command is typically used with the output from a single test
221         information about individual test units and the output from
222         failed tests. It's mainly useful for debugging test failures.
224         The 'summary' format provides outputs the results of one test
225         per line with the test's overall status (OK, SKIPPED, or
229         systems. It provides an XML representation of test
231         information about test failures. Since many JUnit parser make
232         assume that test names look like Java packet strings, the
238         with the show command to merge multiple test results into one
244                         help="Pickled test results")
263         "test",
265         help='Probe test results and set exit code',
268         Load one or more pickled test file and return an exit code
269         corresponding to the test outcome. The following exit codes
277         2: At least one test failed to run. This is what the summary
281         verify its output. When displaying test output using the
282         summary formatter, such a test would show up as 'CHANGED'.
286                         help="Pickled test results")
302         assert False, "Unexpected return status from test"
308     "test" : (_test, _test_args),
316         This tool provides an interface to gem5's test framework that
317         doesn't depend on gem5's build system. It supports test
320         The list sub-command (e.g., "test.py list arm/quick") produces