All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: osstest service owner <osstest-admin@xenproject.org>
Cc: Julien Grall <julien.grall@citrix.com>,
	xen-devel@lists.xensource.com,
	Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [xen-unstable test] 60076: regressions - FAIL
Date: Wed, 29 Jul 2015 11:05:18 +0200	[thread overview]
Message-ID: <1438160718.16912.16.camel@citrix.com> (raw)
In-Reply-To: <osstest-60076-mainreport@xen.org>


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

On Wed, 2015-07-29 at 06:42 +0000, osstest service owner wrote:
> flight 60076 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/60076/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 59817
>  test-armhf-armhf-xl-multivcpu 14 guest-start.2            fail REGR. vs. 59817
>
I gave a quick look at the logs, and didn't spot any obvious issues.

AFAICT, it seems it was actually working:

--- ---
http://logs.test-lab.xenproject.org/osstest/logs/60076/test-armhf-armhf-xl-multivcpu/serial-arndale-metrocentre.log
Jul 28 20:22:21.525058 [  623.706988] device vif2.0 entered promiscuous mode

Jul 28 20:22:21.669108 [  623.713782] IPv6: ADDRCONF(NETDEV_UP): vif2.0: link is not ready

Jul 28 20:22:21.677039 [  625.296200] xen-blkback:ring-ref 8, event-channel 3, protocol 1 (arm-abi) persistent grants

Jul 28 20:22:23.261086 [  625.325256] xen-blkback:ring-ref 9, event-channel 4, protocol 1 (arm-abi) persistent grants

Jul 28 20:22:23.293017 [  625.400219] IPv6: ADDRCONF(NETDEV_CHANGE): vif2.0: link becomes ready

Jul 28 20:22:23.365065 [  625.405368] xenbr0: port 2(vif2.0) entered forwarding state

Jul 28 20:22:23.365110 [  625.410948] xenbr0: port 2(vif2.0) entered forwarding state

http://logs.test-lab.xenproject.org/osstest/logs/60076/test-armhf-armhf-xl-multivcpu/arndale-metrocentre---var-log-xen-console-guest-debian.guest.osstest.log
INIT: Entering runlevel: 2

[^[[36minfo^[[39;49m] Using makefile-style concurrent boot in runlevel 2.
[....] Starting enhanced syslogd: rsyslogd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
[....] Starting periodic command scheduler: cron^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
[....] Starting OpenBSD Secure Shell server: sshd^[[?25l^[[?1c^[7^[[1G[^[[32m ok ^[[39;49m^[8^[[?25h^[[?0c.
^[[r^[[H^[[J

^[[r^[[H^[[J

Debian GNU/Linux 7 debian hvc0

debian login: Debian GNU/Linux 7 debian hvc0

debian login: 

--- ---

Can it be that things are "just" slow, since we're creating a 4 vcpus
guest on a 1 pcpu (not so powerful, I guess) host?

http://logs.test-lab.xenproject.org/osstest/logs/60076/test-armhf-armhf-xl-multivcpu/arndale-metrocentre-output-xl_info_-n
cpu_topology           :
cpu:    core    socket     node
  0:       0        0        0

http://logs.test-lab.xenproject.org/osstest/logs/60076/test-armhf-armhf-xl-multivcpu/arndale-metrocentre-output-xl_vcpu-list
Name                                ID  VCPU   CPU State   Time(s) Affinity (Hard / Soft)
Domain-0                             0     0    0   r--     337.5  all / all
debian.guest.osstest                 2     0    0   ---      13.5  all / all
debian.guest.osstest                 2     1    0   ---      12.9  all / all
debian.guest.osstest                 2     2    0   ---      12.2  all / all
debian.guest.osstest                 2     3    0   ---      12.5  all / all

If I missed something, and this is just completely off... 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: 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-07-29  9:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29  6:42 [xen-unstable test] 60076: regressions - FAIL osstest service owner
2015-07-29  9:05 ` Dario Faggioli [this message]
2015-07-29 14:10   ` Julien Grall
2015-07-29 14:15     ` Julien Grall
2015-07-29 18:18       ` Arndale secondary CPU boot issue Was " Julien Grall
2015-07-30  8:55         ` Ian Campbell
2015-07-30 10:54           ` Stefano Stabellini
2015-07-30 11:27             ` Ian Campbell
2015-07-30 11:27             ` David Vrabel
2015-07-30 11:36           ` Julien Grall
2015-07-30 10:38         ` Andrew Cooper
2015-07-30  7:48       ` 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=1438160718.16912.16.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=julien.grall@citrix.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 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.