All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>,
	Julien Grall <julien.grall@arm.com>,
	Stefano Stabellini <sstabellini@kernel.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: [linux-linus test] 104684: regressions - FAIL
Date: Thu, 26 Jan 2017 14:01:06 -0500	[thread overview]
Message-ID: <90405142-aa96-e6ec-7f51-23871a6de48f@oracle.com> (raw)
In-Reply-To: <22666.12120.495901.409579@mariner.uk.xensource.com>

On 01/26/2017 12:18 PM, Ian Jackson wrote:
> Boris Ostrovsky writes ("Re: [Xen-devel] [linux-linus test] 104684: regressions - FAIL"):
>> On 01/26/2017 08:23 AM, osstest service owner wrote:
>>> flight 104684 linux-linus real [real]
>>> http://logs.test-lab.xenproject.org/osstest/logs/104684/
>>>
>>> Regressions :-(
>>>
>>> Tests which did not succeed and are blocking,
>>> including tests which could not be run:
>>>  test-armhf-armhf-xl           6 xen-boot          fail REGR. vs. 59254
> ...
>> I don't see why ARM tests fail. But then I also don't see (in the serial
>> log) the output of 4.10.0-rc5 being booted. There is U-Boot loading it
>> but there it nothing coming to the console from it.
> Yes.
>
> Unfortunately the osstest bisector is having some trouble with this
> because the basis revision combination includes Xen f3a7ca02400d which
> is ancient and doesn't build now on armhf, although it built before.
> (I think the difference is that the compiler has been updated by
> Debian.)
>
> Since there is no output from Xen, I think this must be a problem with
> the Xen image, not anything to do with Linux.
>
> The history for this test is here:
>   http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/linux-linus
>
> In xen-unstable, there is what looks like a different failure:
>   http://logs.test-lab.xenproject.org/osstest/logs/104681/test-armhf-armhf-xl/serial-arndale-westfield.log
>
> The machine in 104684 is cubietruck-metzinger which seems fine:
>   http://logs.test-lab.xenproject.org/osstest/results/host/cubietruck-metzinger.html

I am probably not interpreting  results correctly but 104684 looks like
failed to me:

http://logs.test-lab.xenproject.org/osstest/logs/104684/test-armhf-armhf-xl/info.html

And 104681's failure looks exactly like 104684.


>
> Here are the histories on the linux-linus and xen-unstable branches:
>   http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/linux-linus
>   http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl/xen-unstable
>
> I think there may be a host-specific bug in ARM in xen-unstable ?

I am not aware of any but I wouldn't know anyway.

-boris

>
>> There is output from 3.16 kernels though.
> I think the 3.16 tests you are refrring to are running with a
> different version of Xen and on different hardware.
>
> Ian.



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-01-26 19:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 13:23 [linux-linus test] 104684: regressions - FAIL osstest service owner
2017-01-26 15:03 ` Boris Ostrovsky
2017-01-26 17:18   ` Ian Jackson
2017-01-26 19:01     ` Boris Ostrovsky [this message]
2017-01-26 21:11       ` Julien Grall
2017-02-14 14:57         ` Julien Grall
2017-02-14 17:42           ` Wei Liu
2017-02-16 14:54             ` Julien Grall
2017-02-22 13:19               ` Ian Jackson
2017-02-22 14:11                 ` Julien Grall
2017-02-24 10:40                   ` Julien Grall
2017-02-24 11:14                     ` Ian Jackson

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=90405142-aa96-e6ec-7f51-23871a6de48f@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.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.