qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: no-reply@patchew.org, qemu-devel@nongnu.org, famz@redhat.com,
	lvivier@redhat.com, peterx@redhat.com
Subject: Re: [Qemu-devel] [PULL 00/16] Migration
Date: Wed, 19 Jul 2017 09:31:01 +0100	[thread overview]
Message-ID: <20170719083101.GC2103@work-vm> (raw)
In-Reply-To: <87379skjm4.fsf@secure.mitica>

* Juan Quintela (quintela@redhat.com) wrote:
> 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.
> 
> > cc: unrecognized option '-no-integrated-as'
> > cc: unrecognized option '-no-integrated-as'
> 
> I hope this is not my fault
>    GTESTER tests/test-vmstate
> 
> > Failed to load simple/primitive:b_1
> > Failed to load simple/primitive:i64_2
> > Failed to load simple/primitive:i32_1
> > Failed to load simple/primitive:i32_1
> > Failed to load test/with_tmp:a
> > Failed to load test/tmp_child_parent:f
> > Failed to load test/tmp_child:parent
> > Failed to load test/with_tmp:tmp
> > Failed to load test/tmp_child:diff
> > Failed to load test/with_tmp:tmp
> > Failed to load test/tmp_child:diff
> > Failed to load test/with_tmp:tmp
> 
> 
> Dave, any good clue?

Those are OK I think - those are the places it purposely generates
a bad stream.

> 
> > ERROR:/tmp/qemu-test/src/tests/test-qga.c:78:fixture_setup: assertion failed (fixture->fd != -1): (-1 != -1)
> > GTester: last random seed: R02Sf37f37a8c5f8ed60d31dbaff962d3c9c

That's the problem; but test-qga is working fine here - and we shouldn't
have gone anywhere near it in these patches.

Dave

> > 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=656d0ada6bee11e794aa525400c803e1', '-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-uic4vhqy/src/docker-src.2017-07-18-15.22.06.26333:/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-uic4vhqy/src'
> > tests/docker/Makefile.include:156: recipe for target 'docker-run-test-quick@centos6' failed
> > make: *** [docker-run-test-quick@centos6] Error 2
> 
> I am pretty sure that this should be a problem somewhere else, not this
> patch, no?
> 
> Thanks, Juan.
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2017-07-19  8:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 15:41 [Qemu-devel] [PULL 00/16] Migration Juan Quintela
2017-07-18 15:41 ` [Qemu-devel] [PULL 01/16] migration/rdma: Fix race on source Juan Quintela
2017-07-18 15:41 ` [Qemu-devel] [PULL 02/16] migration: Close file on failed migration load Juan Quintela
2017-07-18 15:41 ` [Qemu-devel] [PULL 03/16] migration/rdma: fix qemu_rdma_block_for_wrid error paths Juan Quintela
2017-07-18 15:41 ` [Qemu-devel] [PULL 04/16] migration/rdma: Allow cancelling while waiting for wrid Juan Quintela
2017-07-18 15:41 ` [Qemu-devel] [PULL 05/16] migration/rdma: Safely convert control types Juan Quintela
2017-07-18 15:41 ` [Qemu-devel] [PULL 06/16] migration/rdma: Send error during cancelling Juan Quintela
2017-07-18 15:41 ` [Qemu-devel] [PULL 07/16] qdev: provide DEFINE_PROP_INT64() Juan Quintela
2017-07-18 15:41 ` [Qemu-devel] [PULL 08/16] migration: export parameters to props Juan Quintela
2017-07-18 15:41 ` [Qemu-devel] [PULL 09/16] migration: export capabilities " Juan Quintela
2017-07-18 15:41 ` [Qemu-devel] [PULL 10/16] migration: introduce migrate_params_check() Juan Quintela
2017-07-18 15:41 ` [Qemu-devel] [PULL 11/16] migration: provide migrate_params_apply() Juan Quintela
2017-07-18 15:41 ` [Qemu-devel] [PULL 12/16] migration: check global params for validity Juan Quintela
2017-07-18 15:41 ` [Qemu-devel] [PULL 13/16] migration: remove check against colo support Juan Quintela
2017-07-18 15:41 ` [Qemu-devel] [PULL 14/16] migration: provide migrate_caps_check() Juan Quintela
2017-07-18 15:41 ` [Qemu-devel] [PULL 15/16] migration: provide migrate_cap_add() Juan Quintela
2017-07-18 15:41 ` [Qemu-devel] [PULL 16/16] migration: check global caps for validity Juan Quintela
2017-07-18 19:40 ` [Qemu-devel] [PULL 00/16] Migration no-reply
2017-07-19  6:48   ` Juan Quintela
2017-07-19  8:31     ` Dr. David Alan Gilbert [this message]
2017-07-19 12:43 ` Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2018-06-27 12:55 Juan Quintela
2018-06-28 15:28 ` Peter Maydell

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=20170719083101.GC2103@work-vm \
    --to=dgilbert@redhat.com \
    --cc=famz@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=no-reply@patchew.org \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).