All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: no-reply@patchew.org
Cc: qemu-devel@nongnu.org, famz@redhat.com, thuth@redhat.com,
	zyimin@linux.vnet.ibm.com, pmorel@linux.vnet.ibm.com,
	agraf@suse.de, borntraeger@de.ibm.com
Subject: Re: [Qemu-devel] [PATCH RFC v2 0/9] s390x: zPCI detangling
Date: Wed, 19 Jul 2017 09:54:02 +0200	[thread overview]
Message-ID: <20170719095402.1b6f4559@gondolin> (raw)
In-Reply-To: <150040553571.87.18375020437747123393@5d477a5b5989>

On Tue, 18 Jul 2017 12:18:56 -0700 (PDT)
no-reply@patchew.org wrote:

> Hi,
> 
> This series failed automatic build test. Please find the testing commands and
> their output below. If you have docker installed, you can probably reproduce it
> locally.
> 
> Subject: [Qemu-devel] [PATCH RFC v2 0/9] s390x: zPCI detangling
> Message-id: 20170718142455.32676-1-cohuck@redhat.com
> Type: series

(...)

> **
> ERROR:/tmp/qemu-test/src/tests/test-qga.c:78:fixture_setup: assertion failed (fixture->fd != -1): (-1 != -1)
> GTester: last random seed: R02S145bd3c9638ff255618113bf40a4288a
> make: *** [check-tests/test-qga] Error 1
> make: *** Waiting for unfinished jobs....
> Could not access KVM kernel module: No such file or directory
> failed to initialize KVM: No such file or directory
> Back to tcg accelerator.
> Could not access KVM kernel module: No such file or directory
> failed to initialize KVM: No such file or directory
> Back to tcg accelerator.
> Could not access KVM kernel module: No such file or directory
> failed to initialize KVM: No such file or directory
> Back to tcg accelerator.
> Could not access KVM kernel module: No such file or directory
> failed to initialize KVM: No such file or directory
> Back to tcg accelerator.
> Could not access KVM kernel module: No such file or directory
> failed to initialize KVM: No such file or directory
> Back to tcg accelerator.
> Could not access KVM kernel module: No such file or directory
> failed to initialize KVM: No such file or directory
> Back to tcg accelerator.
> Could not access KVM kernel module: No such file or directory
> failed to initialize KVM: No such file or directory
> Back to tcg accelerator.
> Could not access KVM kernel module: No such file or directory
> failed to initialize KVM: No such file or directory
> Back to tcg accelerator.
> Could not access KVM kernel module: No such file or directory
> failed to initialize KVM: No such file or directory
> Back to tcg accelerator.
> Could not access KVM kernel module: No such file or directory
> failed to initialize KVM: No such file or directory
> Back to tcg accelerator.
> Traceback (most recent call last):
>   File "./tests/docker/docker.py", line 382, in <module>
>     sys.exit(main())
>   File "./tests/docker/docker.py", line 379, in main
>     return args.cmdobj.run(args, argv)
>   File "./tests/docker/docker.py", line 237, in run
>     return Docker().run(argv, args.keep, quiet=args.quiet)
>   File "./tests/docker/docker.py", line 205, in run
>     quiet=quiet)
>   File "./tests/docker/docker.py", line 123, 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=79b610ca6beb11e79abf525400c803e1', '-u', '0', '-t', '--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', '/var/tmp/patchew-tester-tmp-4gcxi1vj/src/docker-src.2017-07-18-15.01.12.14950:/var/tmp/qemu:z,ro', '-v', '/root/.cache/qemu-docker-ccache:/var/tmp/ccache:z', 'qemu:centos6', '/var/tmp/qemu/run', 'test-quick']' returned non-zero exit status 2
> tests/docker/Makefile.include:124: recipe for target 'docker-run' failed
> make[1]: *** [docker-run] Error 1
> make[1]: Leaving directory '/var/tmp/patchew-tester-tmp-4gcxi1vj/src'
> tests/docker/Makefile.include:156: recipe for target 'docker-run-test-quick@centos6' failed
> make: *** [docker-run-test-quick@centos6] Error 2
> === OUTPUT END ===
> 
> Test command exited with code: 2

This looks like an unrelated failure which seems to have happened for
various serieses that had been posted.

  reply	other threads:[~2017-07-19  7:54 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 14:24 [Qemu-devel] [PATCH RFC v2 0/9] s390x: zPCI detangling Cornelia Huck
2017-07-18 14:24 ` [Qemu-devel] [PATCH RFC v2 1/9] kvm: remove hard dependency on pci Cornelia Huck
2017-07-18 15:00   ` Thomas Huth
2017-07-18 15:20     ` Cornelia Huck
2017-07-18 14:24 ` [Qemu-devel] [PATCH RFC v2 2/9] s390x/pci: add stubs Cornelia Huck
2017-07-19  7:42   ` Thomas Huth
2017-07-18 14:24 ` [Qemu-devel] [PATCH RFC v2 3/9] s390x: chsc nt2 events are pci-only Cornelia Huck
2017-07-19  7:57   ` Thomas Huth
2017-07-19  8:05     ` Cornelia Huck
2017-07-18 14:24 ` [Qemu-devel] [PATCH RFC v2 4/9] s390x/pci: do not advertise pci on non-pci builds Cornelia Huck
2017-07-18 19:56   ` Christian Borntraeger
2017-07-19  8:00     ` Cornelia Huck
2017-07-19  8:56       ` Yi Min Zhao
2017-07-19  9:24         ` Cornelia Huck
2017-07-19  9:27           ` Yi Min Zhao
2017-07-19  9:38             ` Yi Min Zhao
2017-07-19 11:41   ` Thomas Huth
2017-07-19 12:18     ` Cornelia Huck
2017-07-18 14:24 ` [Qemu-devel] [PATCH RFC v2 5/9] s390x/ccw: create s390 phb conditionally Cornelia Huck
2017-07-19  8:00   ` Thomas Huth
2017-07-18 14:24 ` [Qemu-devel] [PATCH RFC v2 6/9] s390x/sclp: properly guard pci-specific functions Cornelia Huck
2017-07-19  8:03   ` Thomas Huth
2017-07-18 14:24 ` [Qemu-devel] [PATCH RFC v2 7/9] s390x/pci: fence off instructions for non-pci Cornelia Huck
2017-07-19  3:21   ` Yi Min Zhao
2017-07-19  7:38     ` Cornelia Huck
2017-07-19  8:07   ` Thomas Huth
2017-07-19  8:49     ` Cornelia Huck
2017-07-18 14:24 ` [Qemu-devel] [PATCH RFC v2 8/9] s390x/kvm: msi route fixup " Cornelia Huck
2017-07-18 14:58   ` Philippe Mathieu-Daudé
2017-07-18 15:22     ` Cornelia Huck
2017-07-19  3:16       ` Yi Min Zhao
2017-07-19  7:09         ` Thomas Huth
2017-07-19  7:30           ` Cornelia Huck
2017-07-19  3:13   ` Yi Min Zhao
2017-07-18 14:24 ` [Qemu-devel] [PATCH RFC v2 9/9] s390x: refine pci dependencies Cornelia Huck
2017-07-18 14:51   ` Thomas Huth
2017-07-18 19:18 ` [Qemu-devel] [PATCH RFC v2 0/9] s390x: zPCI detangling no-reply
2017-07-19  7:54   ` Cornelia Huck [this message]
2017-07-19 13:03 ` Cornelia Huck
2017-07-19 13:31   ` Thomas Huth
2017-07-24 10:44     ` Christian Borntraeger
2017-08-07 15:46       ` Cornelia Huck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170719095402.1b6f4559@gondolin \
    --to=cohuck@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=famz@redhat.com \
    --cc=no-reply@patchew.org \
    --cc=pmorel@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=zyimin@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.