Re: [Qemu-devel] [PATCH 0/8] tests: Run device-crash-test on "make check"

[Eduardo Habkost <ehabkost@redhat.com>]

On Fri, Mar 09, 2018 at 12:48:42PM -0800, no-reply@patchew.org wrote:
[...]
> /tmp/qemu-test/src/scripts/device-crash-test -q -t machine=DEFAULT accel=tcg --  x86_64-softmmu/qemu-system-x86_64  aarch64-softmmu/qemu-system-aarch64
> /usr/bin/env: python2.7: No such file or directory
> make: *** [check-device-crash-quick] Error 127
> make: *** Waiting for unfinished jobs....
> make: *** wait: No child processes.  Stop.
> Traceback (most recent call last):
>   File "./tests/docker/docker.py", line 407, in <module>
>     sys.exit(main())
>   File "./tests/docker/docker.py", line 404, in main
>     return args.cmdobj.run(args, argv)
>   File "./tests/docker/docker.py", line 261, in run
>     return Docker().run(argv, args.keep, quiet=args.quiet)
>   File "./tests/docker/docker.py", line 229, in run
>     quiet=quiet)
>   File "./tests/docker/docker.py", line 147, in _do_check
>     return subprocess.check_call(self._command + cmd, **kwargs)
>   File "/usr/lib64/python2.7/subprocess.py", line 186, in check_call
>     raise CalledProcessError(retcode, cmd)
> subprocess.CalledProcessError: Command '['docker', 'run', '--label', 'com.qemu.instance.uuid=02a6de1c23db11e8935d52540069c830', '-u', '0', '--security-opt', 'seccomp=unconfined', '--rm', '--net=none', '-e', 'TARGET_LIST=', '-e', 'EXTRA_CONFIGURE_OPTS=', '-e', 'V=', '-e', 'J=8', '-e', 'DEBUG=', '-e', 'SHOW_ENV=1', '-e', 'CCACHE_DIR=/var/tmp/ccache', '-v', '/root/.cache/qemu-docker-ccache:/var/tmp/ccache:z', '-v', '/var/tmp/patchew-tester-tmp-i0mjl1iv/src/docker-src.2018-03-09-15.46.46.18385:/var/tmp/qemu:z,ro', 'qemu:centos6', '/var/tmp/qemu/run', 'test-quick']' returned non-zero exit status 2
> make[1]: *** [tests/docker/Makefile.include:129: docker-run] Error 1
> make[1]: Leaving directory '/var/tmp/patchew-tester-tmp-i0mjl1iv/src'
> make: *** [tests/docker/Makefile.include:163: docker-run-test-quick@centos6] Error 2

Porting device-crash-test to Python 3 is on my plans, but I don't
think this should block us from running device-crash-test on
systems using Python 2.7.  I will look for a mechanism to skip
running device-crash-test if only Python 3 is available.

-- 
Eduardo