From: Julien Grall <julien.grall@arm.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Ian Jackson <ian.jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [linux-linus test] 104237: regressions - FAIL
Date: Thu, 19 Jan 2017 21:37:12 +0100 [thread overview]
Message-ID: <6c4e4369-8dd2-b1c7-4731-41eb237f7e3c@arm.com> (raw)
In-Reply-To: <92528e65-9661-e0ef-0c76-e622a622d9f9@oracle.com>
Hi,
On 19/01/2017 20:15, Boris Ostrovsky wrote:
>
>> So this appears to be a pretty slow, 2-core box:
>>
>> [ 0.049778] SMP: Total of 2 processors activated (96.00 BogoMIPS).
>
> For comparison, my (old-ish) phone is 4 x 26 BogoMIPS. So it's
> theoretically faster than this server.
The ARM32 platforms we have in the colo are not server but development
board :). Some of them are based on early revision of cores and can be
really really really really ... slow.
>
> -boris
>
>>
>> Julien --- how does 2.5 hours for kernel build sound to you? (make -j4
>> all modules)
I would not be surprised that it takes 2.5 hours for a make allmodules
on both the Cubietruck and Arndale.
I have looked at the Linux-3.18 test flights, I know that this thread is
linux-linus but not other flight log can be found. So surprisingly the
time betwen the last two flights of Linus 3.18 has doubled (see [1] and
[2]).
The major difference is a Cubietruck is used on the latest version and a
Arndale on the previous one. I am be surprised that the Cubietruck is
slower than the Arndale. Oh well..
The interesting bit is the build time on the Cubietruck is very close to
the threshold. It is likely that the latest kernel have more modules to
build which increased the time to build.
So I can see 2 solutions:
1) Increase the timeout
2) Only build the kernel on the Arndales. Though they are known to be
unreliable in the colo :/
Any opinions?
Cheers,
[1]
http://logs.test-lab.xenproject.org/osstest/logs/104271/build-armhf-pvops/info.html
[2]
http://logs.test-lab.xenproject.org/osstest/logs/103983/build-armhf-pvops/info.html
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-19 20:37 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 15:05 [linux-linus test] 104237: regressions - FAIL osstest service owner
2017-01-05 1:52 ` Xen 4.8 + Linux 4.9 + Credit2 = can't bootup Konrad Rzeszutek Wilk
2017-01-05 2:05 ` Andrew Cooper
2017-01-05 8:39 ` Dario Faggioli
2017-01-05 9:33 ` Anshul Makkar
2017-01-05 2:10 ` Konrad Rzeszutek Wilk
2017-01-05 3:13 ` Boris Ostrovsky
2017-01-06 15:55 ` Boris Ostrovsky
2017-01-12 12:50 ` Dario Faggioli
2017-01-12 16:22 ` Boris Ostrovsky
2017-01-12 16:41 ` Dario Faggioli
2017-01-12 18:27 ` Ian Jackson
2017-01-13 3:20 ` Boris Ostrovsky
2017-01-13 8:31 ` Dario Faggioli
2017-01-13 15:39 ` Boris Ostrovsky
2017-01-13 16:27 ` Ian Jackson
2017-01-13 23:13 ` Boris Ostrovsky
2017-01-16 11:38 ` Ian Jackson
2017-01-19 11:36 ` Xen 4.8 + Linux 4.9 + Credit2 = can't bootup [and 1 more messages] Ian Jackson
2017-01-16 15:38 ` Xen 4.8 + Linux 4.9 + Credit2 = can't bootup Roger Pau Monné
2017-01-16 15:39 ` Ian Jackson
2017-01-12 18:24 ` Ian Jackson
2017-01-19 17:06 ` [linux-linus test] 104237: regressions - FAIL Boris Ostrovsky
2017-01-19 16:23 ` [linux-linus bisection] complete test-amd64-amd64-xl-qemut-win7-amd64 osstest service owner
2017-01-19 18:05 ` [linux-linus bisection] complete test-amd64-amd64-xl-qemut-win7-amd64 [and 1 more messages] Ian Jackson
2017-01-19 18:44 ` Boris Ostrovsky
2017-01-20 11:09 ` Ian Jackson
2017-01-20 16:29 ` Boris Ostrovsky
2017-01-20 16:59 ` Boris Ostrovsky
2017-01-19 18:07 ` [linux-linus test] 104237: regressions - FAIL Ian Jackson
2017-01-19 19:09 ` Boris Ostrovsky
2017-01-19 19:15 ` Boris Ostrovsky
2017-01-19 20:37 ` Julien Grall [this message]
2017-01-19 21:01 ` Boris Ostrovsky
2017-01-20 12:06 ` Ian Jackson
2017-01-23 12:16 ` Ian Jackson
2017-01-23 14:31 ` Boris Ostrovsky
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=6c4e4369-8dd2-b1c7-4731-41eb237f7e3c@arm.com \
--to=julien.grall@arm.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ian.jackson@eu.citrix.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.