From: Julien Grall <julien.grall@arm.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>, xen-devel@lists.xenproject.org
Cc: Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [OSSTEST PATCH 3/3] make-flight: Shed some ARM64 load
Date: Mon, 22 May 2017 16:49:04 +0100 [thread overview]
Message-ID: <c9aa5278-cf39-93c7-3ceb-2a2b0c44960d@arm.com> (raw)
In-Reply-To: <1495467922-30085-3-git-send-email-ian.jackson@eu.citrix.com>
Hi Ian,
On 22/05/17 16:45, Ian Jackson wrote:
> Currently we have only two ARM64 boxes and now that the builds are
> passing, the tests have become a bottleneck. Cut them down for now.
>
> This patch should be reverted when we have more ARM64 capacity, which
> is being looked into.
>
> We drop these tests:
>
> test-arm64-arm64-xl-multivcpu
> test-arm64-arm64-xl-rtds
> test-arm64-arm64-libvirt
> test-arm64-arm64-libvirt-qcow2
>
> We drop all these on all branches, except:
>
> linux-arm-xen
> libvirt
NIT: The indentation look different here :).
>
> (Verified with
> OSSTEST_CONFIG=standalone-config-example eatmydata ./standalone-generate-dump-flight-runvars
> Of course the libvirt branches lack the xl tests already.)
>
> CC: Julien Grall <julien.grall@arm.com>
> CC: Stefano Stabellini <sstabellini@kernel.org>
> Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
FWIW:
Acked-by: Julien Grall <julien.grall@arm.com>
Cheers,
> ---
> make-flight | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/make-flight b/make-flight
> index 39ef6de..7833605 100755
> --- a/make-flight
> +++ b/make-flight
> @@ -104,6 +104,19 @@ job_create_test_filter_callback () {
> local xenarch=$1; shift
> local dom0arch=$1; shift
>
> + # cut down the arm64 tests temporarily, due to lack of capacity
> + case "$branch" in
> + *arm*|*libvirt*) ;;
> + *)
> + case "$job" in
> + test-arm64-arm64-xl-multivcpu) return 1 ;;
> + test-arm64-arm64-xl-rtds) return 1 ;;
> + test-arm64-arm64-libvirt) return 1 ;;
> + test-arm64-arm64-libvirt-qcow2) return 1 ;;
> + esac
> + ;;
> + esac
> +
> case "$branch" in
> xen-unstable-smoke)
> case "$job" in
>
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-05-22 15:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <osstest-109837-mainreport@xen.org>
2017-05-22 15:45 ` [OSSTEST PATCH 1/3] host examination: Actually permanently save the logs Ian Jackson
2017-05-22 15:45 ` [OSSTEST PATCH 2/3] ap-common: Switch to Linux 4.9 by default Ian Jackson
2017-05-23 13:03 ` Roger Pau Monné
2017-05-30 14:28 ` Nested virt broken in Linux 4.9 (was Re: [OSSTEST PATCH 2/3] ap-common: Switch to Linux 4.9 by default [and 1 more messages]) Ian Jackson
2017-05-30 14:57 ` Boris Ostrovsky
2017-05-30 15:47 ` Ian Jackson
2017-05-30 15:53 ` Julien Grall
2017-05-30 16:13 ` Ian Jackson
2017-05-30 16:15 ` Julien Grall
2017-05-30 16:22 ` Ian Jackson
2017-06-06 11:16 ` Ian Jackson
2017-06-06 15:56 ` Julien Grall
2017-05-22 15:45 ` [OSSTEST PATCH 3/3] make-flight: Shed some ARM64 load Ian Jackson
2017-05-22 15:49 ` Julien Grall [this message]
2017-05-23 13:08 ` [OSSTEST PATCH 1/3] host examination: Actually permanently save the logs Roger Pau Monné
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=c9aa5278-cf39-93c7-3ceb-2a2b0c44960d@arm.com \
--to=julien.grall@arm.com \
--cc=ian.jackson@eu.citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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).