All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: osstest service user <osstest@xenbits.xen.org>
Cc: Meng Xu <xumengpanda@gmail.com>,
	xen-devel@lists.xensource.com, ian.jackson@eu.citrix.com,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [xen-unstable test] 58974: regressions - FAIL
Date: Tue, 30 Jun 2015 19:14:22 +0200	[thread overview]
Message-ID: <1435684462.25170.315.camel@citrix.com> (raw)
In-Reply-To: <osstest-58974-mainreport@xen.org>


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

Hey Meng,

you wanted to "get in touch" with OSSTest failures for RTDS, didn't you?
Well, Here you go! :-P

[I'm adding IanC and Julien, as this is ARM related]

On Tue, 2015-06-30 at 05:18 +0000, osstest service user wrote:
> flight 58974 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/58974/
>
So, have a look at the link above, and search 'rtds' in the webpage.

You'll see that test is passing on x86:
http://logs.test-lab.xenproject.org/osstest/logs/58974/test-amd64-amd64-xl-rtds/info.html

But it's failing on ARM:
http://logs.test-lab.xenproject.org/osstest/logs/58974/test-armhf-armhf-xl-rtds/info.html

As it's said here as well:
> Tests which did not succeed, but are not blocking:
>  test-amd64-amd64-xl-pvh-intel 11 guest-start                  fail  never pass
>  test-amd64-amd64-xl-pvh-amd  11 guest-start                  fail   never pass
>  test-armhf-armhf-xl-rtds     11 guest-start                  fail   never pass

It is, apparently, constantly and consistently failing on ARM, as shown
by the history of the job, on the xen-unstable branch:
http://logs.test-lab.xenproject.org/osstest/results/history/test-armhf-armhf-xl-rtds/xen-unstable

To actually see what happens, check the details of the job, and the
content of the various captured logs and files.

For instance, here's the serial console output:
http://logs.test-lab.xenproject.org/osstest/logs/58974/test-armhf-armhf-xl-rtds/serial-arndale-bluewater.log

Go to the bottom of it, you'll find the splat.

Hope this has been helpful... if you'd b able to have a look at what's
happening, that would be awesome. If you don't have time, I will have a
look myself, but only in a few days.

Thanks and 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: 181 bytes --]

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

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

  reply	other threads:[~2015-06-30 17:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30  5:18 [xen-unstable test] 58974: regressions - FAIL osstest service user
2015-06-30 17:14 ` Dario Faggioli [this message]
2015-07-02  4:29   ` Meng Xu
2015-07-02  8:49     ` Dario Faggioli

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=1435684462.25170.315.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=osstest@xenbits.xen.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=xumengpanda@gmail.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.