xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>,
	xen-devel@lists.xensource.com
Cc: Juergen Gross <jgross@suse.com>,
	Julien Grall <julien.grall@arm.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [linux-4.9 test] 110371: regressions - FAIL
Date: Tue, 13 Jun 2017 12:33:57 +0200	[thread overview]
Message-ID: <1497350037.26212.37.camel@citrix.com> (raw)
In-Reply-To: <osstest-110371-mainreport@xen.org>


[-- Attachment #1.1: Type: text/plain, Size: 1865 bytes --]

On Tue, 2017-06-13 at 03:58 +0000, osstest service owner wrote:
> flight 110371 linux-4.9 real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/110371/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-armhf-armhf-xl-credit2   6 xen-boot                 fail REGR.
> vs. 107358
> 
This caught my attention because of the 'credit2' part. I therefore
went checking and noticed from here:
http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl-credit2/ALL

and here:
http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl-credit2/ALL

That the test has been repeatedly failing, when on the linux-4.9
branch, always on arndale-bluewater.

I've checked a couple of serial logs of failing flights, and they all
look similar.

I've then looked here:
http://logs.test-lab.xenproject.org/osstest/results/host/arndale-bluewater.html

And seen that other jobs (not only -credit2 ones) are failing as well,
and in similar ways, when using the linux-4.9 branch:
http://logs.test-lab.xenproject.org/osstest/logs/110371/test-armhf-armhf-xl-multivcpu/info.html
http://logs.test-lab.xenproject.org/osstest/logs/110371/test-armhf-armhf-xl-vhd/info.html

Finally, test-armhf-armhf-xl-credit2 passes, on arndale-bluewater, when
on the linux-linus branch.

So, this appears to be something related to linux-4.9 and that
particular board, I guess?

(If this was known and being looked up already, sorry for the noise.)

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

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

  reply	other threads:[~2017-06-13 10:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13  3:58 [linux-4.9 test] 110371: regressions - FAIL osstest service owner
2017-06-13 10:33 ` Dario Faggioli [this message]
2017-06-13 12:13   ` Ian Jackson
2017-06-19  9:48     ` Julien Grall
2017-06-19 13:03       ` 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=1497350037.26212.37.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=julien.grall@arm.com \
    --cc=osstest-admin@xenproject.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 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).