xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [libvirt bisection] complete build-armhf-libvirt
Date: Sat, 31 Oct 2015 05:00:57 +0000	[thread overview]
Message-ID: <E1ZsOHh-0004tA-R5@osstest.test-lab.xenproject.org> (raw)

branch xen-unstable
xen branch xen-unstable
job build-armhf-libvirt
test libvirt-build

Tree: libvirt git://libvirt.org/libvirt.git
Tree: libvirt_gnulib git://git.sv.gnu.org/gnulib.git
Tree: qemuu git://xenbits.xen.org/qemu-xen.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:  0f7436ca54c9db2d5460bd54e7613f64f4727102
  Bug not present: 131e7245a8336541ee61047eac8ecb447129b963


  commit 0f7436ca54c9db2d5460bd54e7613f64f4727102
  Author: Maxim Perevedentsev <mperevedentsev@virtuozzo.com>
  Date:   Tue Oct 20 18:44:18 2015 +0300
  
      network: wait for DAD to finish for bridge IPv6 addresses
      
      commit db488c79 assumed that dnsmasq would complete IPv6 DAD before
      daemonizing, but in reality it doesn't wait, which creates problems
      when libvirt's bridge driver sets the matching "dummy tap device" to
      IFF_DOWN prior to DAD completing.
      
      This patch waits for DAD completion by periodically polling the kernel
      using netlink to check whether there are any IPv6 addresses assigned
      to bridge which have a 'tentative' state (if there are any in this
      state, then DAD hasn't yet finished). After DAD is finished, execution
      continues. To avoid an endless hang in case something was wrong with
      the kernel's DAD, we wait a maximum of 5 seconds.


For bisection revision-tuple graph see:
   http://logs.test-lab.xenproject.org/osstest/results/bisect/libvirt/build-armhf-libvirt.libvirt-build.html
Revision IDs in each graph node refer, respectively, to the Trees above.

----------------------------------------
Running cs-bisection-step --graph-out=/home/logs/results/bisect/libvirt/build-armhf-libvirt.libvirt-build --summary-out=tmp/63394.bisection-summary --basis-template=63340 --blessings=real,real-bisect libvirt build-armhf-libvirt libvirt-build
Searching for failure / basis pass:
 63352 fail [host=arndale-westfield] / 63340 ok.
Failure / basis pass flights: 63352 / 63340
Tree: libvirt git://libvirt.org/libvirt.git
Tree: libvirt_gnulib git://git.sv.gnu.org/gnulib.git
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen git://xenbits.xen.org/xen.git
Latest 0f7436ca54c9db2d5460bd54e7613f64f4727102 f39477dba778e99392948dd3dd19ec0d46aee932 816609b2841297925a223ec377c336360e044ee5 e08f3834c2f375153f104c827dd7c2fea93b288e
Basis pass 3c7590e0a435d833895fc7b5be489e53e223ad95 f39477dba778e99392948dd3dd19ec0d46aee932 816609b2841297925a223ec377c336360e044ee5 e08f3834c2f375153f104c827dd7c2fea93b288e
Generating revisions with ./adhoc-revtuple-generator  git://libvirt.org/libvirt.git#3c7590e0a435d833895fc7b5be489e53e223ad95-0f7436ca54c9db2d5460bd54e7613f64f4727102 git://git.sv.gnu.org/gnulib.git#f39477dba778e99392948dd3dd19ec0d46aee932-f39477dba778e99392948dd3dd19ec0d46aee932 git://xenbits.xen.org/qemu-xen.git#816609b2841297925a223ec377c336360e044ee5-816609b2841297925a223ec377c336360e044ee5 git://xenbits.xen.org/xen.git#e08f3834c2f375153f104c827dd7c2fea93b288e-e08f3834c2f375153f104c827dd7c2fea93b288e
Loaded 1001 nodes in revision graph
Searching for test results:
 63352 fail 0f7436ca54c9db2d5460bd54e7613f64f4727102 f39477dba778e99392948dd3dd19ec0d46aee932 816609b2841297925a223ec377c336360e044ee5 e08f3834c2f375153f104c827dd7c2fea93b288e
 63340 pass 3c7590e0a435d833895fc7b5be489e53e223ad95 f39477dba778e99392948dd3dd19ec0d46aee932 816609b2841297925a223ec377c336360e044ee5 e08f3834c2f375153f104c827dd7c2fea93b288e
 63370 pass 3c7590e0a435d833895fc7b5be489e53e223ad95 f39477dba778e99392948dd3dd19ec0d46aee932 816609b2841297925a223ec377c336360e044ee5 e08f3834c2f375153f104c827dd7c2fea93b288e
 63386 fail 0f7436ca54c9db2d5460bd54e7613f64f4727102 f39477dba778e99392948dd3dd19ec0d46aee932 816609b2841297925a223ec377c336360e044ee5 e08f3834c2f375153f104c827dd7c2fea93b288e
 63387 pass 4eac55238f856d29d07a60448adb2e0b2f8e28b5 f39477dba778e99392948dd3dd19ec0d46aee932 816609b2841297925a223ec377c336360e044ee5 e08f3834c2f375153f104c827dd7c2fea93b288e
 63388 pass 131e7245a8336541ee61047eac8ecb447129b963 f39477dba778e99392948dd3dd19ec0d46aee932 816609b2841297925a223ec377c336360e044ee5 e08f3834c2f375153f104c827dd7c2fea93b288e
 63389 fail 0f7436ca54c9db2d5460bd54e7613f64f4727102 f39477dba778e99392948dd3dd19ec0d46aee932 816609b2841297925a223ec377c336360e044ee5 e08f3834c2f375153f104c827dd7c2fea93b288e
 63390 pass 131e7245a8336541ee61047eac8ecb447129b963 f39477dba778e99392948dd3dd19ec0d46aee932 816609b2841297925a223ec377c336360e044ee5 e08f3834c2f375153f104c827dd7c2fea93b288e
 63392 fail 0f7436ca54c9db2d5460bd54e7613f64f4727102 f39477dba778e99392948dd3dd19ec0d46aee932 816609b2841297925a223ec377c336360e044ee5 e08f3834c2f375153f104c827dd7c2fea93b288e
 63393 pass 131e7245a8336541ee61047eac8ecb447129b963 f39477dba778e99392948dd3dd19ec0d46aee932 816609b2841297925a223ec377c336360e044ee5 e08f3834c2f375153f104c827dd7c2fea93b288e
 63394 fail 0f7436ca54c9db2d5460bd54e7613f64f4727102 f39477dba778e99392948dd3dd19ec0d46aee932 816609b2841297925a223ec377c336360e044ee5 e08f3834c2f375153f104c827dd7c2fea93b288e
Searching for interesting versions
 Result found: flight 63340 (pass), for basis pass
 Result found: flight 63352 (fail), for basis failure
 Repro found: flight 63370 (pass), for basis pass
 Repro found: flight 63386 (fail), for basis failure
 0 revisions at 131e7245a8336541ee61047eac8ecb447129b963 f39477dba778e99392948dd3dd19ec0d46aee932 816609b2841297925a223ec377c336360e044ee5 e08f3834c2f375153f104c827dd7c2fea93b288e
No revisions left to test, checking graph state.
 Result found: flight 63388 (pass), for last pass
 Result found: flight 63389 (fail), for first failure
 Repro found: flight 63390 (pass), for last pass
 Repro found: flight 63392 (fail), for first failure
 Repro found: flight 63393 (pass), for last pass
 Repro found: flight 63394 (fail), for first failure

*** Found and reproduced problem changeset ***

  Bug is in tree:  libvirt git://libvirt.org/libvirt.git
  Bug introduced:  0f7436ca54c9db2d5460bd54e7613f64f4727102
  Bug not present: 131e7245a8336541ee61047eac8ecb447129b963


  commit 0f7436ca54c9db2d5460bd54e7613f64f4727102
  Author: Maxim Perevedentsev <mperevedentsev@virtuozzo.com>
  Date:   Tue Oct 20 18:44:18 2015 +0300
  
      network: wait for DAD to finish for bridge IPv6 addresses
      
      commit db488c79 assumed that dnsmasq would complete IPv6 DAD before
      daemonizing, but in reality it doesn't wait, which creates problems
      when libvirt's bridge driver sets the matching "dummy tap device" to
      IFF_DOWN prior to DAD completing.
      
      This patch waits for DAD completion by periodically polling the kernel
      using netlink to check whether there are any IPv6 addresses assigned
      to bridge which have a 'tentative' state (if there are any in this
      state, then DAD hasn't yet finished). After DAD is finished, execution
      continues. To avoid an endless hang in case something was wrong with
      the kernel's DAD, we wait a maximum of 5 seconds.

Revision graph left in /home/logs/results/bisect/libvirt/build-armhf-libvirt.libvirt-build.{dot,ps,png,html}.
----------------------------------------
63394: tolerable ALL FAIL

flight 63394 libvirt real-bisect [real]
http://logs.test-lab.xenproject.org/osstest/logs/63394/

Failures :-/ but no regressions.

Tests which did not succeed,
including tests which could not be run:
 build-armhf-libvirt           5 libvirt-build           fail baseline untested


jobs:
 build-armhf-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

             reply	other threads:[~2015-10-31  5:00 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-31  5:00 osstest service owner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-05-30  4:47 [libvirt bisection] complete build-armhf-libvirt osstest service owner
2018-11-20 13:10 osstest service owner
2018-06-09 22:55 osstest service owner
2018-01-16  5:32 osstest service owner
2017-04-29  0:43 osstest service owner
2017-03-25 13:19 osstest service owner
2016-06-16  6:30 osstest service owner
2016-05-22 11:23 osstest service owner
2016-04-18 19:27 osstest service owner
2016-03-21  3:34 osstest service owner
2015-08-17 21:53 osstest service owner
2015-04-16 21:46 osstest service user
2015-04-17  9:54 ` Ian Campbell
2015-01-19  4:48 xen.org
2015-01-19  9:37 ` Ian Campbell
2014-11-23  2:02 xen.org
2014-10-16 23:42 xen.org
2014-09-26  8:07 xen.org
2014-09-12 22:19 xen.org
2014-09-08 18:30 xen.org

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=E1ZsOHh-0004tA-R5@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).