From: Joao Martins <joao.m.martins@oracle.com>
To: osstest service owner <osstest-admin@xenproject.org>,
xen-devel@lists.xensource.com
Subject: Re: [libvirt bisection] complete build-i386-libvirt
Date: Fri, 15 Jul 2016 14:16:44 +0100 [thread overview]
Message-ID: <5788E23C.40700@oracle.com> (raw)
In-Reply-To: <E1bO2lV-0005j5-AU@osstest.test-lab.xenproject.org>
On 07/15/2016 02:02 PM, osstest service owner wrote:
> branch xen-unstable
> xenbranch xen-unstable
> job build-i386-libvirt
> testid 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/qemu-xen-traditional.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: 6381c89f8cce23afbc67e5979b0b5e304a09db16
> Bug not present: fe2d37295eeb6bfa6345cfa9648edbec58d0c485
> Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/97367/
>
>
> commit 6381c89f8cce23afbc67e5979b0b5e304a09db16
> Author: Daniel P. Berrange <berrange@redhat.com>
> Date: Thu Jul 7 16:52:47 2016 +0100
>
> virconf: add typed value accessor methods
>
> Currently many users of virConf APIs are defining the same
> macros for calling virConfValue() and then doing type
> checking. To remove this repeated code, add a set of
> typesafe accessor methods.
>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
>
>
> For bisection revision-tuple graph see:
> http://logs.test-lab.xenproject.org/osstest/results/bisect/libvirt/build-i386-libvirt.libvirt-build.html
> Revision IDs in each graph node refer, respectively, to the Trees above.
FYI, This was already fixed in commit b7caf4fcd ("virConfGetValueSSizeT: Fix build on
32 bits")
Joao
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-15 13:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 13:02 [libvirt bisection] complete build-i386-libvirt osstest service owner
2016-07-15 13:16 ` Joao Martins [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-24 9:44 osstest service owner
2018-08-16 19:50 osstest service owner
2018-01-14 7:04 osstest service owner
2017-04-28 5:15 osstest service owner
2017-03-29 17:35 osstest service owner
2016-11-03 21:12 osstest service owner
2016-06-15 9:35 osstest service owner
2016-05-27 16:59 osstest service owner
2016-05-21 10:58 osstest service owner
2016-04-17 21:34 osstest service owner
2016-04-11 19:01 osstest service owner
2016-02-03 10:28 osstest service owner
2015-12-15 4:26 osstest service owner
2015-12-15 22:37 ` Jim Fehlig
2015-08-17 9:23 osstest service owner
2015-01-18 10:23 xen.org
2014-12-11 2:09 xen.org
2014-09-26 4:48 xen.org
2014-09-26 15:13 ` Ian Campbell
2014-09-26 15:29 ` Ian Jackson
2014-09-26 16:26 ` Ian Campbell
2014-07-12 1:21 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=5788E23C.40700@oracle.com \
--to=joao.m.martins@oracle.com \
--cc=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 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.