mirror of
https://github.com/checkpoint-restore/criu
synced 2025-08-27 12:28:14 +00:00
eba1fba8b3
Install sudo, create test user with ID 1000, install bash,
fix pidfile creation and pidfile chmod.
v2:
* use sleep to give the criu daemon some time to start up
v3:
* Andrei is of course right and sleep is not good solution.
After adding --status-fd support to criu service, this
is how we now detect that criu is ready.
v4:
* This was much more complicated than expected which is related
to the different versions of the tools on the different travis
test targets. There seems to be a bug in bash on Ubuntu
https://lists.gnu.org/archive/html/bug-bash/2017-07/msg00039.html
which prevents using 'read -n1' on Ubuntu. As a workaround
the result from CRIU's status FD is now read via python.
Another problem was discovered on alpine with the loop restore test.
CRIU says to use setsid even if the process is already using setsid.
As a workaround, still with setsid, this process is now using
shell-job true for checkpoint and restore.
Parts of v2 have been committed before. So the changes from this commit
are partially already in another commit.
Signed-off-by: Adrian Reber <areber@redhat.com>
Signed-off-by: Andrei Vagin <avagin@virtuozzo.com>
46 lines
1.3 KiB
Python
Executable File
46 lines
1.3 KiB
Python
Executable File
#!/usr/bin/python2
|
|
|
|
import socket, os, imp, sys
|
|
import rpc_pb2 as rpc
|
|
import argparse
|
|
|
|
parser = argparse.ArgumentParser(description="Test ability to restore a process from images using CRIU RPC")
|
|
parser.add_argument('socket', type = str, help = "CRIU service socket")
|
|
parser.add_argument('dir', type = str, help = "Directory where CRIU images could be found")
|
|
|
|
args = vars(parser.parse_args())
|
|
|
|
# Connect to service socket
|
|
s = socket.socket(socket.AF_UNIX, socket.SOCK_SEQPACKET)
|
|
s.connect(args['socket'])
|
|
|
|
# Create criu msg, set it's type to dump request
|
|
# and set dump options. Checkout more options in protobuf/rpc.proto
|
|
req = rpc.criu_req()
|
|
req.type = rpc.RESTORE
|
|
req.opts.images_dir_fd = os.open(args['dir'], os.O_DIRECTORY)
|
|
# As the dumped process is running with setsid this should not
|
|
# be necessary. There seems to be a problem for this testcase
|
|
# in combination with alpine's setsid.
|
|
# The dump is now done with -j and the restore also.
|
|
req.opts.shell_job = True
|
|
|
|
# Send request
|
|
s.send(req.SerializeToString())
|
|
|
|
# Recv response
|
|
resp = rpc.criu_resp()
|
|
MAX_MSG_SIZE = 1024
|
|
resp.ParseFromString(s.recv(MAX_MSG_SIZE))
|
|
|
|
if resp.type != rpc.RESTORE:
|
|
print 'Unexpected msg type'
|
|
sys.exit(-1)
|
|
else:
|
|
if resp.success:
|
|
print 'Restore success'
|
|
else:
|
|
print 'Restore fail'
|
|
sys.exit(-1)
|
|
print "PID of the restored program is %d\n" %(resp.restore.pid)
|