From: Ian Jackson <ian.jackson@eu.citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [linux-linus bisection] complete test-amd64-amd64-xl-qemut-win7-amd64 [and 1 more messages]
Date: Fri, 20 Jan 2017 11:09:22 +0000 [thread overview]
Message-ID: <22657.61410.949927.536885@mariner.uk.xensource.com> (raw)
In-Reply-To: <1e906253-01b0-da34-6cc8-0e4e29c63f75@oracle.com>
Boris Ostrovsky writes ("Re: [linux-linus bisection] complete test-amd64-amd64-xl-qemut-win7-amd64 [and 1 more messages]"):
> On 01/19/2017 01:05 PM, Ian Jackson wrote:
> > This means that the bug is in commits which diverged before the last
> > pass of this test.
> >
> > (Did your filters get you a copy of the bisection email?)
>
> No, I haven't set a filter for the bisector but I did see this message
> and didn't find bisection results particularly useful. bcc981e9ed84 is
> from about a year ago, which, I think, is when you stopped running this
> test. And so the question might be whether "Bug not present" is really true?
It means that this precise combination of software was tested and
passed, recently, on the same hosts, several times.
See
http://logs.test-lab.xenproject.org/osstest/results/bisect/linux-linus/test-amd64-amd64-xl-qemut-win7-amd64.xen-boot.html
where you can see the flight numbers. (They are sequential.)
So yes it is really true.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-20 11:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 15:05 [linux-linus test] 104237: regressions - FAIL osstest service owner
2017-01-05 1:52 ` Xen 4.8 + Linux 4.9 + Credit2 = can't bootup Konrad Rzeszutek Wilk
2017-01-05 2:05 ` Andrew Cooper
2017-01-05 8:39 ` Dario Faggioli
2017-01-05 9:33 ` Anshul Makkar
2017-01-05 2:10 ` Konrad Rzeszutek Wilk
2017-01-05 3:13 ` Boris Ostrovsky
2017-01-06 15:55 ` Boris Ostrovsky
2017-01-12 12:50 ` Dario Faggioli
2017-01-12 16:22 ` Boris Ostrovsky
2017-01-12 16:41 ` Dario Faggioli
2017-01-12 18:27 ` Ian Jackson
2017-01-13 3:20 ` Boris Ostrovsky
2017-01-13 8:31 ` Dario Faggioli
2017-01-13 15:39 ` Boris Ostrovsky
2017-01-13 16:27 ` Ian Jackson
2017-01-13 23:13 ` Boris Ostrovsky
2017-01-16 11:38 ` Ian Jackson
2017-01-19 11:36 ` Xen 4.8 + Linux 4.9 + Credit2 = can't bootup [and 1 more messages] Ian Jackson
2017-01-16 15:38 ` Xen 4.8 + Linux 4.9 + Credit2 = can't bootup Roger Pau Monné
2017-01-16 15:39 ` Ian Jackson
2017-01-12 18:24 ` Ian Jackson
2017-01-19 17:06 ` [linux-linus test] 104237: regressions - FAIL Boris Ostrovsky
2017-01-19 16:23 ` [linux-linus bisection] complete test-amd64-amd64-xl-qemut-win7-amd64 osstest service owner
2017-01-19 18:05 ` [linux-linus bisection] complete test-amd64-amd64-xl-qemut-win7-amd64 [and 1 more messages] Ian Jackson
2017-01-19 18:44 ` Boris Ostrovsky
2017-01-20 11:09 ` Ian Jackson [this message]
2017-01-20 16:29 ` Boris Ostrovsky
2017-01-20 16:59 ` Boris Ostrovsky
2017-01-19 18:07 ` [linux-linus test] 104237: regressions - FAIL Ian Jackson
2017-01-19 19:09 ` Boris Ostrovsky
2017-01-19 19:15 ` Boris Ostrovsky
2017-01-19 20:37 ` Julien Grall
2017-01-19 21:01 ` Boris Ostrovsky
2017-01-20 12:06 ` Ian Jackson
2017-01-23 12:16 ` Ian Jackson
2017-01-23 14:31 ` Boris Ostrovsky
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=22657.61410.949927.536885@mariner.uk.xensource.com \
--to=ian.jackson@eu.citrix.com \
--cc=boris.ostrovsky@oracle.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.