2,257
edits
Changes
no edit summary
=== All zdtm tests ===
=== All zdtm tests ===
You can run all the tests by:
You can run all the tests by:
test/zdtm.py
test/zdtm.py
{{Out|There's a known issue with BTRFS spoiling dev_t values for files and sockets! Not all tests will work on it.}}
{{Out|There's a known issue with BTRFS spoiling dev_t values for files and sockets! Not all tests will work on it.}}
This would run the tests in basic variation -- run the test, checkpoint, restore, check for results.
There are more variations, each is an option to the zdtm.py. Here they are:
;--nocr
: would do start test and check results. User to check that test themselves are working.
.
;--norst
: would start the test, the checkpoint it leaving the tests run, then check the results. Used to check that checkpoint is not destructive.
;--iter <number>
: would start the test, then would checkpoint and restore it the <number> times. Used to check that after restore tests are in checkpoint-able state.
;--pre <number>
: would statr the test, then do <number> pre-dumps, then checkpoint, restore and check results. Used to check that pre-dumps work.
;--page-server
: would run tests, but dumps (and pre-dumps) will go through the [[page server]].
;--sibling
: would run tests, but restore would happen in so called ''sibling'' mode. Used by LXC and Docker.
;--snaps (in conjunction with --pre)
: instead of pre-dumps do full dumps
;--user (only works with --norst)
: check how criu works when run from non-root.
=== Certain test ===
=== Certain test ===