1,067
edits
Changes
→Specific tests: some formatting
You can run a single test with
You can run a single test with
zdtm.py run -t <test-name>
zdtm.py run -t ''test-name''
The simplest test is <code>zdtm/static/env00</code>. It has the bare minimal a process might have -- a little bit of memory, a signal handler and one opened file. If CRIU cannot C/R ''this'' test, it's surely cannot do anything.
The simplest test is <code>zdtm/static/env00</code>. It has the bare minimal a process might have -- a little bit of memory, a signal handler and one opened file. If CRIU cannot C/R '''this''' test, it surely cannot do anything else.
You can also run only the test proggies themselves manually by issuing the
You can also run only the test proggies themselves manually by issuing the
make <testname>.pid
make ''test-name''.pid
command. After you've done c/r-ing it you should run
command. After you've done c/r-ing it you should run
If you don't want to mess with this, you can use the <code>zdtm.py run</code> script. When launched with the "-a" option it runs all the tests one-by-one. The exact test can be specified by a command line argument. The <code>list</code> command lists the tests it can run.
make ''test-name''.out
and check for the ''test-name''.out file contents.
If you don't want to mess with this, you can use the <code>zdtm.py run</code> script. When launched with the <code>-a</code> option, it runs all the tests one-by-one. The exact test can be specified by a command line argument. The <code>list</code> command lists the tests it can run.
== See also ==
== See also ==