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: xen-devel@lists.xensource.com, ian.jackson@eu.citrix.com,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [xen-unstable test] 58618: regressions - FAIL
Date: Wed, 17 Jun 2015 11:59:51 +0200	[thread overview]
Message-ID: <1434535191.24348.4.camel@citrix.com> (raw)
In-Reply-To: <osstest-58618-mainreport@xen.org>


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

On Wed, 2015-06-17 at 09:05 +0000, osstest service user wrote:
> flight 58618 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/58618/
> 
> 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. 58392
> 
I just gave a look at this, expecting to find something similar/related
to the last failure (which was
http://logs.test-lab.xenproject.org/osstest/logs/58330/test-armhf-armhf-xl-credit2/info.html on a cubietruck).

However, looking at the logs in:
http://logs.test-lab.xenproject.org/osstest/logs/58618/test-armhf-armhf-xl-credit2/info.html

I don't see anything stuck, like last time, nor I see anything that
might be credit2 related.

Actually, it really seems to me that the box did succeed in rebooting in
Xen, as requested, but it suffered from networking issues:

device eth0 entered promiscuous mode
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6: ADDRCONF(NETDEV_UP): xenbr0: link is not ready
Waiting for xenbr0 to get ready (MAXWAIT is 2 seconds).
asix 1-3.2.4:1.0 eth0: link down
...
Starting MTA:
Starting NTP server: ntpd
asix 1-3.2.4:1.0 eth0: link down

Is this something known already and/or expected?

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-17  9:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-17  9:05 [xen-unstable test] 58618: regressions - FAIL osstest service user
2015-06-17  9:59 ` Dario Faggioli [this message]
2015-06-17 10:12   ` 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=1434535191.24348.4.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 \
    /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.