xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 06 Jul 2015 12:06:53 -0400	[thread overview]
Message-ID: <559AA79D.6060808@oracle.com> (raw)
In-Reply-To: <1436197741.25646.121.camel@citrix.com>

On 07/06/2015 11:49 AM, Ian Campbell wrote:
> On Mon, 2015-07-06 at 11:22 -0400, Boris Ostrovsky wrote:
>> On 07/06/2015 04:32 AM, Ian Campbell wrote:
>>> On Fri, 2015-07-03 at 22:21 +0000, osstest service owner wrote:
>>>> flight 59041 linux-3.18 real [real]
>>>> http://logs.test-lab.xenproject.org/osstest/logs/59041/
>>>>
>>>> Regressions :-(
>>>>
>>>> Tests which did not succeed and are blocking,
>>>> including tests which could not be run:
>>>>    test-amd64-amd64-xl-pvh-intel 11 guest-start              fail REGR. vs. 58581
>>> Not really sure who is on the hook for pvh fails these days, copying
>>> some likely suspects + x86 maintainers. Looks like the guest is triple
>>> faulting.
>>
>> Looks like something happened between 2015-06-15 and 2015-06-29 (flights
>> 58581 and 58976)
> Yes, and a bit of the original report I should have quoted is:
>
> version targeted for testing:
>   linux                ea5dd38e93b3bec3427e5d3eef000bbf5d637e76
> baseline version:
>   linux                d048c068d00da7d4cfa5ea7651933b99026958cf
>
> See also the complete history of this test on this branch at
> http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-amd64-xl-pvh-intel/linux-3.18.html
>
>>   and it's only 3.18 kernel, right?
> As far as I know. But: older linux-X.Y doesn't support PVH, so this test
> has always failed at guest-start in those flights, before we would have
> gotten to this failure.
>
> The only newer stable branch which we test is linux-4.1, flight 59054
> from didn't show this issue, but the next one might pick up something
> newer, or 4.1.(y+1) might still be in the pipeline upstream and  the
> issue will show up later.
>
> We also test linux-linus and linux-next, so far neither of them seems to
> exhibit this problem:
> http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-amd64-xl-pvh-intel/linux-linus.html
> http://logs.test-lab.xenproject.org/osstest/results/history/test-amd64-amd64-xl-pvh-intel/linux-next.html
>
> Which is interesting in itself I suppose.
>
> 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.

BTW, our last test on Xen4.6/linux4.1+ was on July 1st and it passed too.

-boris

  reply	other threads:[~2015-07-06 16:06 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 [this message]
2015-07-07  7:39         ` Ian Campbell
2015-07-07 14:55           ` Boris Ostrovsky
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=559AA79D.6060808@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 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).