From: Ian Campbell <Ian.Campbell@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, keir@xen.org,
stefano.stabellini@eu.citrix.com
Subject: Re: [libvirt bisection] complete build-i386-libvirt
Date: Fri, 26 Sep 2014 17:26:38 +0100 [thread overview]
Message-ID: <1411748798.31592.25.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <21541.34395.257286.819840@mariner.uk.xensource.com>
On Fri, 2014-09-26 at 16:29 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-devel] [libvirt bisection] complete build-i386-libvirt"):
> > This seems odd to me.
> >
> > Given the failures happening recently are:
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/30391/
> > http://www.chiark.greenend.org.uk/~xensrcts/logs/30391/build-amd64-libvirt/5.ts-libvirt-build.log
> ...
> > It seems more likely that "Add common API for doing polkit
> > authentication" which was fingered by the other build-*-libvirt
> > bisections is far more plausible.
>
> Yes.
>
> > I'm not sure what caused the bisector go off back into July. Perhaps a
> > spurious failure at some point sent it down a rat hole?
>
> I think that's likely. The basis pass it found was very old. And the
> commit it fingered was indeed bad (and reported as such at the time).
> It's just that since then the tree was fixed and became bad again.
Makes sense.
It was pretty timely too, so it clearly didn't spend ages bisecting the
last 4 months...
>
> Ian.
next prev parent reply other threads:[~2014-09-26 16:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 4:48 [libvirt bisection] complete build-i386-libvirt xen.org
2014-09-26 15:13 ` Ian Campbell
2014-09-26 15:29 ` Ian Jackson
2014-09-26 16:26 ` Ian Campbell [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-07-15 13:02 osstest service owner
2016-07-15 13:16 ` Joao Martins
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-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=1411748798.31592.25.camel@kazak.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@eu.citrix.com \
--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).