Difference between revisions of "ZDTM test suite"

From CRIU
Jump to: navigation, search
(Running)
Line 8: Line 8:
 
       make test
 
       make test
 
or by:
 
or by:
       test/zdtm.sh
+
       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.}}

Revision as of 16:40, 29 February 2016

Description

ZDTM stands for zero-down-time-migration. It's test suite developed for testing how OpenVZ live migration works. We use this test suite for checking how criu do their job. The suit consists of many small atomic tests -- each puts a process into some "state" (opens a file, maps a memory segment, puts data in a pipe, etc.), then asks to be checkpointed and restored. The in checks that the "state" was preserved (file is still open, memory is still mapped, pipe contains what was put into it).

Running

All zdtm tests

You can run all the tests by:

      make test

or by:

      test/zdtm.py

There's a known issue with BTRFS spoiling dev_t values for files and sockets! Not all tests will work on it.

Certain test

You can also run the tests manually by issuing a

      make <testname>.pid

command. After you've done c/r-ing it you should run

      make <testname>.out

and check for the <testname>.out file contents.

If you don't want to mess with this you can use the zdtm.sh script. When launched without arguments runs all the tests one-by-one. The exact test can be specified by the command line argument. The -l option lists the tests it can run.