From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: Elena Ufimtseva <elena.ufimtseva@oracle.com>,
xen-devel@lists.xensource.com,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
ian.jackson@eu.citrix.com, Jan Beulich <JBeulich@suse.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [linux-3.18 test] 59041: regressions - trouble: blocked/broken/fail/pass
Date: Tue, 07 Jul 2015 10:55:58 -0400 [thread overview]
Message-ID: <559BE87E.4050506@oracle.com> (raw)
In-Reply-To: <1436254763.17598.117.camel@citrix.com>
On 07/07/2015 03:39 AM, Ian Campbell wrote:
> On Mon, 2015-07-06 at 12:06 -0400, Boris Ostrovsky wrote:
>>> Bisection was broken for linux-3.18 until this morning, Ian fixed the
>>> config and it should pick up on this failure and start investigating
>>> once the next flight completes (tonight some time).
>> OK, I'll wait until tomorrow then to see if it (the bisection) is
>> successful.
> After flight 59075 failed it has now started, progress is recorded at:
>
> http://logs.test-lab.xenproject.org/osstest/results/bisect/linux-3.18/test-amd64-amd64-xl-pvh-intel.guest-start.html
>
> It's currently reproducing the baseline pass (the double line around a
> cell indicates what it is currently testing). The hashes in each cell
> are in the same order as the tree list at the top, i.e Linux is the
> first entry and Xen is the last.
>
> Scheduling wise I don't think it is going to have made very much
> progress by the time you get in today though.
So it is bisecting all five trees, right? (Well, four -- firmware hashes
don't seem to be changing).
And if I assume that the issue is with kernel (which may not be a good
assumption, but for the sake of my understanding of how the graph works)
then d048c068d00d (green) was good and ea5dd38e93b3 (red) is bad? What
about the one right below red (d24b9b8d95f0) --- is it bad or good?
-boris
next prev parent reply other threads:[~2015-07-07 14:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 22:21 [linux-3.18 test] 59041: regressions - trouble: blocked/broken/fail/pass osstest service owner
2015-07-06 8:27 ` Ian Campbell
2015-07-06 8:28 ` Ian Campbell
2015-07-06 10:16 ` Ian Jackson
2015-07-06 10:33 ` Ian Campbell
2015-07-06 8:32 ` Ian Campbell
2015-07-06 15:22 ` Boris Ostrovsky
2015-07-06 15:49 ` Ian Campbell
2015-07-06 16:06 ` Boris Ostrovsky
2015-07-07 7:39 ` Ian Campbell
2015-07-07 14:55 ` Boris Ostrovsky [this message]
2015-07-07 15:00 ` Ian Jackson
2015-07-07 15:08 ` Ian Campbell
2015-07-07 15:16 ` Boris Ostrovsky
2015-07-07 19:22 ` Boris Ostrovsky
2015-07-07 19:45 ` Ian Campbell
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=559BE87E.4050506@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=elena.ufimtseva@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=roger.pau@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 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.