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

2018-03-09 Thread Eduardo Habkost
On Fri, Mar 09, 2018 at 12:48:42PM -0800, no-re...@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 
> 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



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

2018-03-09 Thread no-reply
Hi,

This series failed docker-quick@centos6 build test. Please find the testing 
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.

Type: series
Message-id: 20180309202827.12085-1-ehabk...@redhat.com
Subject: [Qemu-devel] [PATCH 0/8] tests: Run device-crash-test on "make check"

=== TEST SCRIPT BEGIN ===
#!/bin/bash
set -e
git submodule update --init dtc
# Let docker tests dump environment info
export SHOW_ENV=1
export J=8
time make docker-test-quick@centos6
=== TEST SCRIPT END ===

Updating 3c8cf5a9c21ff8782164d1def7f44bd888713384
Switched to a new branch 'test'
43e25ed8f6 tests: Run device-crash-test on "make check"
41b49d1214 device-crash-test: Don't print warnings in quiet mode
b693bd7177 device-crash-test: Use WARN for known crashes
c593d69f22 device-crash-test: Remove runnable-machine check
5340dee618 device-crash-test: New known crashes
0481610e19 device-crash-test: Accept machine=DEFAULT to test the default machine
183fe35b74 device-crash-test: Add examples to script documentation
6b368c2850 device-crash-test: Refactor loglevel configuration code

=== OUTPUT BEGIN ===
Submodule 'dtc' (git://git.qemu-project.org/dtc.git) registered for path 'dtc'
Cloning into '/var/tmp/patchew-tester-tmp-i0mjl1iv/src/dtc'...
Submodule path 'dtc': checked out 'e54388015af1fb4bf04d0bca99caba1074d9cc42'
  BUILD   centos6
make[1]: Entering directory '/var/tmp/patchew-tester-tmp-i0mjl1iv/src'
  GEN 
/var/tmp/patchew-tester-tmp-i0mjl1iv/src/docker-src.2018-03-09-15.46.46.18385/qemu.tar
Cloning into 
'/var/tmp/patchew-tester-tmp-i0mjl1iv/src/docker-src.2018-03-09-15.46.46.18385/qemu.tar.vroot'...
done.
Your branch is up-to-date with 'origin/test'.
Submodule 'dtc' (git://git.qemu-project.org/dtc.git) registered for path 'dtc'
Cloning into 
'/var/tmp/patchew-tester-tmp-i0mjl1iv/src/docker-src.2018-03-09-15.46.46.18385/qemu.tar.vroot/dtc'...
Submodule path 'dtc': checked out 'e54388015af1fb4bf04d0bca99caba1074d9cc42'
Submodule 'ui/keycodemapdb' (git://git.qemu.org/keycodemapdb.git) registered 
for path 'ui/keycodemapdb'
Cloning into 
'/var/tmp/patchew-tester-tmp-i0mjl1iv/src/docker-src.2018-03-09-15.46.46.18385/qemu.tar.vroot/ui/keycodemapdb'...
Submodule path 'ui/keycodemapdb': checked out 
'6b3d716e2b6472eb7189d3220552280ef3d832ce'
  COPYRUNNER
RUN test-quick in qemu:centos6 
Packages installed:
SDL-devel-1.2.14-7.el6_7.1.x86_64
bison-2.4.1-5.el6.x86_64
bzip2-devel-1.0.5-7.el6_0.x86_64
ccache-3.1.6-2.el6.x86_64
csnappy-devel-0-6.20150729gitd7bc683.el6.x86_64
flex-2.5.35-9.el6.x86_64
gcc-4.4.7-18.el6.x86_64
gettext-0.17-18.el6.x86_64
git-1.7.1-9.el6_9.x86_64
glib2-devel-2.28.8-9.el6.x86_64
libepoxy-devel-1.2-3.el6.x86_64
libfdt-devel-1.4.0-1.el6.x86_64
librdmacm-devel-1.0.21-0.el6.x86_64
lzo-devel-2.03-3.1.el6_5.1.x86_64
make-3.81-23.el6.x86_64
mesa-libEGL-devel-11.0.7-4.el6.x86_64
mesa-libgbm-devel-11.0.7-4.el6.x86_64
package g++ is not installed
pixman-devel-0.32.8-1.el6.x86_64
spice-glib-devel-0.26-8.el6.x86_64
spice-server-devel-0.12.4-16.el6.x86_64
tar-1.23-15.el6_8.x86_64
vte-devel-0.25.1-9.el6.x86_64
xen-devel-4.6.6-2.el6.x86_64
zlib-devel-1.2.3-29.el6.x86_64

Environment variables:
PACKAGES=bison bzip2-devel ccache csnappy-devel flex g++
 gcc gettext git glib2-devel libepoxy-devel libfdt-devel
 librdmacm-devel lzo-devel make mesa-libEGL-devel 
mesa-libgbm-devel pixman-devel SDL-devel spice-glib-devel 
spice-server-devel tar vte-devel xen-devel zlib-devel
HOSTNAME=19c8ab59833a
MAKEFLAGS= -j8
J=8
CCACHE_DIR=/var/tmp/ccache
EXTRA_CONFIGURE_OPTS=
V=
SHOW_ENV=1
PATH=/usr/lib/ccache:/usr/lib64/ccache:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/
TARGET_LIST=
SHLVL=1
HOME=/root
TEST_DIR=/tmp/qemu-test
FEATURES= dtc
DEBUG=
_=/usr/bin/env

Configure options:
--enable-werror --target-list=x86_64-softmmu,aarch64-softmmu 
--prefix=/tmp/qemu-test/install
No C++ compiler available; disabling C++ specific optional code
Install prefix/tmp/qemu-test/install
BIOS directory/tmp/qemu-test/install/share/qemu
firmware path /tmp/qemu-test/install/share/qemu-firmware
binary directory  /tmp/qemu-test/install/bin
library directory /tmp/qemu-test/install/lib
module directory  /tmp/qemu-test/install/lib/qemu
libexec directory /tmp/qemu-test/install/libexec
include directory /tmp/qemu-test/install/include
config directory  /tmp/qemu-test/install/etc
local state directory   /tmp/qemu-test/install/var
Manual directory  /tmp/qemu-test/install/share/man
ELF interp prefix /usr/gnemul/qemu-%M
Source path   /tmp/qemu-test/src
GIT binarygit
GIT submodules
C compilercc
Host C compiler   cc
C++ compiler  
Objective-C compiler cc
ARFLAGS   rv
CFLAGS-O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -g 
QEMU_CFLAGS   -I/usr/include/pixman-1   -I$(SRC_PATH)/dtc/libfdt -pthread 
-I/usr/include/glib-2.0 -

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

2018-03-09 Thread Eduardo Habkost
So, we're back to that time when we need to add new known crashes
to device-crash-test, because we haven't been running it in a
while and new bugs were introduced.

To help prevent this from happening again, this series adds new
rules to validate devices against the default machine-type on
"make check".  This should help us catch more obvious bugs, at
least.

Peter, is it possible to get this tested inside your system that
validates every pull request, just to see if it won't generate
any unexpected warning, error, or false positive?

Eduardo Habkost (8):
  device-crash-test: Refactor loglevel configuration code
  device-crash-test: Add examples to script documentation
  device-crash-test: Accept machine=DEFAULT to test the default machine
  device-crash-test: New known crashes
  device-crash-test: Remove runnable-machine check
  device-crash-test: Use WARN for known crashes
  device-crash-test: Don't print warnings in quiet mode
  tests: Run device-crash-test on "make check"

 scripts/device-crash-test | 135 ++
 tests/Makefile.include|  13 -
 2 files changed, 88 insertions(+), 60 deletions(-)

-- 
2.14.3