From: Julien Grall <julien.grall@arm.com>
To: Rich Persaud <persaur@gmail.com>
Cc: xen-devel@lists.xenproject.org,
Ian Jackson <ian.jackson@eu.citrix.com>,
Lars Kurth <lars.kurth@citrix.com>
Subject: Re: [OSSTEST PATCH] production-config: Temporarily drop arm64
Date: Wed, 15 Aug 2018 10:29:16 +0100 [thread overview]
Message-ID: <db6c1c13-963a-e6cf-08cd-d67833a4956d@arm.com> (raw)
In-Reply-To: <D83DD9A9-9F5A-45BB-A3C8-AC65B0F6D700@gmail.com>
Hi,
On 08/15/2018 12:25 AM, Rich Persaud wrote:
> On Aug 14, 2018, at 18:46, Julien Grall <julien.grall@arm.com> wrote:
>>
>> Hi Rich,
>>
>>> On 08/14/2018 11:42 PM, Rich Persaud wrote:
>>>> On Aug 13, 2018, at 10:57, Ian Jackson <ian.jackson@eu.citrix.com> wrote:
>>>>
>>>> Both our arm64 boxes are out of commission and repairing them is
>>>> taking too long.
>>> Apologies if this is already documented elsewhere - does OSStest use Qemu for arm64 testing?
>>
>> Osstest does not use QEMU for testing, but I think it would be too slow to have result in timely manner and use x86 resource as well.
>
> To avoid having zero test coverage for one target architecture, it may be acceptable to temporarily reduce test capacity for other target architectures. QEMU has the advantage of being faster to "rack" a test architecture for temporary use.
Well, arm64 test coverage was already reduced because we had only 2
platforms ready for testing. I can hardly imagine how this code be
reduced more for fitting QEMU. Beware that we compile natively in
Osstest so this will take an awful lot of time here.
However, the main problem here is not the lack of platform but the lack
of time for OSSTest team (mostly Ian and Wei) to investigate and
bring-up new platforms. Maybe you can help finding contributors to help
on Arm64?
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-08-15 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 14:57 [OSSTEST PATCH] production-config: Temporarily drop arm64 Ian Jackson
2018-08-13 15:02 ` Julien Grall
2018-08-14 22:42 ` Rich Persaud
2018-08-14 22:46 ` Julien Grall
2018-08-14 23:25 ` Rich Persaud
2018-08-15 9:29 ` Julien Grall [this message]
2018-08-15 15:04 ` Rich Persaud
2019-01-29 13:42 ` Ian Jackson
-- strict thread matches above, loose matches on Subject: below --
2018-11-20 16:17 Ian Jackson
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=db6c1c13-963a-e6cf-08cd-d67833a4956d@arm.com \
--to=julien.grall@arm.com \
--cc=ian.jackson@eu.citrix.com \
--cc=lars.kurth@citrix.com \
--cc=persaur@gmail.com \
--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).