Lines Matching refs:run
7 …d comments at the bottom of the tutorials and test source files that describes the tests to be run.
8 …arses the tutorial and test source files and generates the makefiles and shell scripts. This is run
9 automatically by the make system and rarely is run directly.
17 describe tests and subtests required to run executables associated with
52 - one or more `mpiexec` tests that run the executable
75 To run these tests one must first clone the datafiles repository and then set the environmental var…
81 inserted to describe the test(s) to be run. The elements of the test are
111 - A reference file with the *expected output from the test run*,
112 the output from the test run is compared with it (with a difftool).
137 to run.
145 - The value of this is the command to be run, for example,
177 the test is run to ensure that stale temporary files are not read.
181 - This is a space-delimited list of run requirements (not build
523 ### Determining the failed jobs of a given run
526 logged the output or run without showing the full error. The best way of
542 To see the list of all tests that failed from the last run, you can also run this command:
597 -f ................ force attempt to run test that would otherwise be skipped
607 -U ................ run cUda-memcheck
608 -V ................ run Valgrind
628 For loops it sometimes can become onerous to run the whole test.
654 Use PETSC_CUDAMEMCHECK_COMMAND to change the executable to run and
660 FORCE=1 Force SKIP or TODO tests to run
661 PRINTONLY=1 Print the command, but do not run. For loops print first command
663 TESTDIR='tests' Subdirectory where tests are run ($PETSC_DIR/$PETSC_ARCH
666 TESTBASE='tests' Subdirectory where tests are run ($PETSC_DIR/$PETSC_ARCH)
690 To re-run the last tests which failed:
701 To compile the test and run it:
918 run independently of each other.
996 3. Provide information on all tests, even those that are not built or run because they do not meet …