From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [libvirt bisection] complete build-amd64-libvirt
Date: Sun, 16 Aug 2015 21:50:02 +0000 [thread overview]
Message-ID: <E1ZR5oY-0004OB-6y@osstest.test-lab.xenproject.org> (raw)
branch xen-unstable
xen branch xen-unstable
job build-amd64-libvirt
test libvirt-build
Tree: libvirt git://libvirt.org/libvirt.git
Tree: libvirt_gnulib git://git.sv.gnu.org/gnulib.git
Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git
Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git
Tree: xen git://xenbits.xen.org/xen.git
*** Found and reproduced problem changeset ***
Bug is in tree: libvirt git://libvirt.org/libvirt.git
Bug introduced: 834c5720e4434f0bcc807bb1cf20855af63e24a3
Bug not present: b5d63e997bb4cbaa3c9d5e35e38998b0c1e78fd1
commit 834c5720e4434f0bcc807bb1cf20855af63e24a3
Author: Erik Skultety <eskultet@redhat.com>
Date: Mon Jun 15 18:53:58 2015 +0200
tools: Introduce new client generic module vsh
In order to share as much virsh' logic as possible with upcomming
virt-admin client we need to split virsh logic into virsh specific and
client generic features.
Since majority of virsh methods should be generic enough to be used by
other clients, it's much easier to rename virsh specific data to virshX
than doing this vice versa. It moved generic virsh commands (including info
and opts structures) to generic module vsh.c.
Besides renaming methods and structures, this patch also involves introduction
of a client specific control structure being referenced as private data in the
original control structure, introduction of a new global vsh Initializer,
which currently doesn't do much, but there is a potential for added
functionality in the future.
Lastly it introduced client hooks which are especially necessary during
client connecting phase.
For bisection revision-tuple graph see:
http://logs.test-lab.xenproject.org/osstest/results/bisect/libvirt/build-amd64-libvirt.libvirt-build.html
Revision IDs in each graph node refer, respectively, to the Trees above.
----------------------------------------
Searching for failure / basis pass:
60708 fail [host=nocera0] / 60681 [host=nocera1] 60663 ok.
Failure / basis pass flights: 60708 / 60663
(tree with no url: ovmf)
(tree with no url: seabios)
Tree: libvirt git://libvirt.org/libvirt.git
Tree: libvirt_gnulib git://git.sv.gnu.org/gnulib.git
Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git
Tree: qemuu git://xenbits.xen.org/staging/qemu-upstream-unstable.git
Tree: xen git://xenbits.xen.org/xen.git
Latest 834c5720e4434f0bcc807bb1cf20855af63e24a3 f39477dba778e99392948dd3dd19ec0d46aee932 7f057440b31da38196e3398fd1b618fc36ad97d6 bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa 201eac83831d94ba2e9a63a7eed4c128633fafb1
Basis pass 133c25c81c9ef79053d8d67a1e897846f9d7adb5 f39477dba778e99392948dd3dd19ec0d46aee932 7f057440b31da38196e3398fd1b618fc36ad97d6 bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa 201eac83831d94ba2e9a63a7eed4c128633fafb1
Generating revisions with ./adhoc-revtuple-generator git://libvirt.org/libvirt.git#133c25c81c9ef79053d8d67a1e897846f9d7adb5-834c5720e4434f0bcc807bb1cf20855af63e24a3 git://git.sv.gnu.org/gnulib.git#f39477dba778e99392948dd3dd19ec0d46aee932-f39477dba778e99392948dd3dd19ec0d46aee932 git://xenbits.xen.org/staging/qemu-xen-unstable.git#7f057440b31da38196e3398fd1b618fc36ad97d6-7f057440b31da38196e3398fd1b618fc36ad97d6 git://xenbits.xen.org/staging/qemu-upstream-unstable.git#bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa-bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa git://xenbits.xen.org/xen.git#201eac83831d94ba2e9a63a7eed4c128633fafb1-201eac83831d94ba2e9a63a7eed4c128633fafb1
+ exec
+ sh -xe
+ cd /home/osstest/repos/libvirt
+ git remote set-url origin git://cache:9419/git://libvirt.org/libvirt.git
+ git fetch -p origin +refs/heads/*:refs/remotes/origin/*
+ exec
+ sh -xe
+ cd /home/osstest/repos/libvirt
+ git remote set-url origin git://cache:9419/git://libvirt.org/libvirt.git
+ git fetch -p origin +refs/heads/*:refs/remotes/origin/*
Loaded 1001 nodes in revision graph
Searching for test results:
60681 [host=nocera1]
60663 pass 133c25c81c9ef79053d8d67a1e897846f9d7adb5 f39477dba778e99392948dd3dd19ec0d46aee932 7f057440b31da38196e3398fd1b618fc36ad97d6 bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa 201eac83831d94ba2e9a63a7eed4c128633fafb1
60716 pass 133c25c81c9ef79053d8d67a1e897846f9d7adb5 f39477dba778e99392948dd3dd19ec0d46aee932 7f057440b31da38196e3398fd1b618fc36ad97d6 bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa 201eac83831d94ba2e9a63a7eed4c128633fafb1
60733 fail 834c5720e4434f0bcc807bb1cf20855af63e24a3 f39477dba778e99392948dd3dd19ec0d46aee932 7f057440b31da38196e3398fd1b618fc36ad97d6 bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa 201eac83831d94ba2e9a63a7eed4c128633fafb1
60708 fail 834c5720e4434f0bcc807bb1cf20855af63e24a3 f39477dba778e99392948dd3dd19ec0d46aee932 7f057440b31da38196e3398fd1b618fc36ad97d6 bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa 201eac83831d94ba2e9a63a7eed4c128633fafb1
60721 pass 1b08cc170a84077afd4d15f4639a9a2cf398e9a2 f39477dba778e99392948dd3dd19ec0d46aee932 7f057440b31da38196e3398fd1b618fc36ad97d6 bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa 201eac83831d94ba2e9a63a7eed4c128633fafb1
60717 fail 834c5720e4434f0bcc807bb1cf20855af63e24a3 f39477dba778e99392948dd3dd19ec0d46aee932 7f057440b31da38196e3398fd1b618fc36ad97d6 bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa 201eac83831d94ba2e9a63a7eed4c128633fafb1
60724 pass ff486e0d29a7c08e7131447ca3c878ed791def4e f39477dba778e99392948dd3dd19ec0d46aee932 7f057440b31da38196e3398fd1b618fc36ad97d6 bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa 201eac83831d94ba2e9a63a7eed4c128633fafb1
60722 pass 151ba022939dad1e562c4156cb62e7a3ade6a7f5 f39477dba778e99392948dd3dd19ec0d46aee932 7f057440b31da38196e3398fd1b618fc36ad97d6 bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa 201eac83831d94ba2e9a63a7eed4c128633fafb1
60726 pass 9877d8406cd32864278dfa7bb040c542782d4cfb f39477dba778e99392948dd3dd19ec0d46aee932 7f057440b31da38196e3398fd1b618fc36ad97d6 bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa 201eac83831d94ba2e9a63a7eed4c128633fafb1
60728 pass b5d63e997bb4cbaa3c9d5e35e38998b0c1e78fd1 f39477dba778e99392948dd3dd19ec0d46aee932 7f057440b31da38196e3398fd1b618fc36ad97d6 bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa 201eac83831d94ba2e9a63a7eed4c128633fafb1
60729 fail 834c5720e4434f0bcc807bb1cf20855af63e24a3 f39477dba778e99392948dd3dd19ec0d46aee932 7f057440b31da38196e3398fd1b618fc36ad97d6 bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa 201eac83831d94ba2e9a63a7eed4c128633fafb1
60730 pass b5d63e997bb4cbaa3c9d5e35e38998b0c1e78fd1 f39477dba778e99392948dd3dd19ec0d46aee932 7f057440b31da38196e3398fd1b618fc36ad97d6 bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa 201eac83831d94ba2e9a63a7eed4c128633fafb1
60731 fail 834c5720e4434f0bcc807bb1cf20855af63e24a3 f39477dba778e99392948dd3dd19ec0d46aee932 7f057440b31da38196e3398fd1b618fc36ad97d6 bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa 201eac83831d94ba2e9a63a7eed4c128633fafb1
60732 pass b5d63e997bb4cbaa3c9d5e35e38998b0c1e78fd1 f39477dba778e99392948dd3dd19ec0d46aee932 7f057440b31da38196e3398fd1b618fc36ad97d6 bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa 201eac83831d94ba2e9a63a7eed4c128633fafb1
Searching for interesting versions
Result found: flight 60663 (pass), for basis pass
Result found: flight 60708 (fail), for basis failure
Repro found: flight 60716 (pass), for basis pass
Repro found: flight 60717 (fail), for basis failure
0 revisions at b5d63e997bb4cbaa3c9d5e35e38998b0c1e78fd1 f39477dba778e99392948dd3dd19ec0d46aee932 7f057440b31da38196e3398fd1b618fc36ad97d6 bcf35eec0b621c46dbf0aeb40c6bc06b5d3981aa 201eac83831d94ba2e9a63a7eed4c128633fafb1
No revisions left to test, checking graph state.
Result found: flight 60728 (pass), for last pass
Result found: flight 60729 (fail), for first failure
Repro found: flight 60730 (pass), for last pass
Repro found: flight 60731 (fail), for first failure
Repro found: flight 60732 (pass), for last pass
Repro found: flight 60733 (fail), for first failure
*** Found and reproduced problem changeset ***
Bug is in tree: libvirt git://libvirt.org/libvirt.git
Bug introduced: 834c5720e4434f0bcc807bb1cf20855af63e24a3
Bug not present: b5d63e997bb4cbaa3c9d5e35e38998b0c1e78fd1
+ exec
+ sh -xe
+ cd /home/osstest/repos/libvirt
+ git remote set-url origin git://cache:9419/git://libvirt.org/libvirt.git
+ git fetch -p origin +refs/heads/*:refs/remotes/origin/*
commit 834c5720e4434f0bcc807bb1cf20855af63e24a3
Author: Erik Skultety <eskultet@redhat.com>
Date: Mon Jun 15 18:53:58 2015 +0200
tools: Introduce new client generic module vsh
In order to share as much virsh' logic as possible with upcomming
virt-admin client we need to split virsh logic into virsh specific and
client generic features.
Since majority of virsh methods should be generic enough to be used by
other clients, it's much easier to rename virsh specific data to virshX
than doing this vice versa. It moved generic virsh commands (including info
and opts structures) to generic module vsh.c.
Besides renaming methods and structures, this patch also involves introduction
of a client specific control structure being referenced as private data in the
original control structure, introduction of a new global vsh Initializer,
which currently doesn't do much, but there is a potential for added
functionality in the future.
Lastly it introduced client hooks which are especially necessary during
client connecting phase.
Revision graph left in /home/logs/results/bisect/libvirt/build-amd64-libvirt.libvirt-build.{dot,ps,png,html}.
----------------------------------------
60733: tolerable ALL FAIL
flight 60733 libvirt real-bisect [real]
http://logs.test-lab.xenproject.org/osstest/logs/60733/
Failures :-/ but no regressions.
Tests which did not succeed,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail baseline untested
jobs:
build-amd64-libvirt fail
------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images
Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs
Explanation of these reports, and of osstest in general, is at
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
next reply other threads:[~2015-08-16 21:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-16 21:50 osstest service owner [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-21 22:25 [libvirt bisection] complete build-amd64-libvirt osstest service owner
2020-05-23 11:48 osstest service owner
2018-11-19 5:17 osstest service owner
2018-08-18 18:24 osstest service owner
2018-06-07 17:35 osstest service owner
2018-01-13 23:36 osstest service owner
2017-04-28 13:17 osstest service owner
2016-11-03 16:19 osstest service owner
2016-06-15 18:59 osstest service owner
2016-05-28 7:15 osstest service owner
2016-05-21 16:23 osstest service owner
2016-04-17 1:57 osstest service owner
2016-04-11 3:44 osstest service owner
2016-02-03 4:13 osstest service owner
2015-12-16 1:25 osstest service owner
2015-09-28 23:09 osstest service owner
2015-01-20 17:20 xen.org
2015-01-06 1:55 xen.org
2014-09-26 17:29 xen.org
2014-07-11 7:06 xen.org
2014-07-11 7:23 ` Olaf Hering
2014-07-11 13:43 ` Ian Campbell
2014-07-11 13:48 ` Olaf Hering
2014-07-11 15:06 ` Jim Fehlig
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=E1ZR5oY-0004OB-6y@osstest.test-lab.xenproject.org \
--to=osstest-admin@xenproject.org \
--cc=xen-devel@lists.xensource.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).