On 6/13/19 6:24 PM, no-re...@patchew.org wrote: > === TEST SCRIPT BEGIN === > #!/bin/bash > time make docker-test-debug@fedora TARGET_LIST=x86_64-softmmu J=14 NETWORK=1 > === TEST SCRIPT END ===
> The full log is available at > http://patchew.org/logs/20190613132000.2146-1-ptosc...@redhat.com/testing.asan/?type=message. === OUTPUT BEGIN === BUILD fedora The command '/bin/sh -c dnf install -y $PACKAGES' returned a non-zero code: 1 Traceback (most recent call last): File "./tests/docker/docker.py", line 615, in <module> sys.exit(main()) File "./tests/docker/docker.py", line 611, in main return args.cmdobj.run(args, argv) File "./tests/docker/docker.py", line 413, in run extra_files_cksum=cksum) File "./tests/docker/docker.py", line 280, in build_image quiet=quiet) File "./tests/docker/docker.py", line 207, in _do_check return subprocess.check_call(self._command + cmd, **kwargs) File "/usr/lib64/python2.7/subprocess.py", line 542, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['sudo', '-n', 'docker', 'build', '-t', 'qemu:fedora', '-f', '/tmp/docker_buildN2FMKc/tmpz_9Up_.docker', '/tmp/docker_buildN2FMKc']' returned non-zero exit status 1 make: *** [docker-image-fedora] Error 1 real 3m54.376s Not sure this is a network issue or something else, should we rebuild docker images with V=1 on patchew?
