From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/4] travis: Remove qemu-riscv64 testing
Date: Thu, 26 Mar 2020 22:01:02 -0400 [thread overview]
Message-ID: <20200327020102.GE5793@bill-the-cat> (raw)
In-Reply-To: <CAEUhbmU_D4bsQ-9W4nAXLGdB9jDqQ=W=mzPDc_4OZx3qjm9tug@mail.gmail.com>
On Fri, Mar 27, 2020 at 09:51:03AM +0800, Bin Meng wrote:
> Hi Tom,
>
> On Fri, Mar 27, 2020 at 12:10 AM Tom Rini <trini@konsulko.com> wrote:
> >
> > On Thu, Mar 26, 2020 at 09:05:21AM -0700, Bin Meng wrote:
> >
> > > As of today there is no pre-built UEFI GRUB image for RISC-V 32/64
> > > available on the internet, and with travis-ci we don't build GRUB
> > > images like we do for azure and gitlab.
> > >
> > > Remove qemu-riscv64 testing temporarily.
> > >
> > > Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
> > > ---
> > >
> > > .travis.yml | 7 -------
> > > 1 file changed, 7 deletions(-)
> > >
> > > diff --git a/.travis.yml b/.travis.yml
> > > index c59bd77..55b94cf 100644
> > > --- a/.travis.yml
> > > +++ b/.travis.yml
> > > @@ -481,13 +481,6 @@ matrix:
> > > QEMU_TARGET="ppc-softmmu"
> > > BUILDMAN="^qemu-ppce500$"
> > > TOOLCHAIN="powerpc"
> > > - - name: "test/py qemu-riscv64"
> > > - env:
> > > - - TEST_PY_BD="qemu-riscv64"
> > > - TEST_PY_TEST_SPEC="not sleep"
> > > - QEMU_TARGET="riscv64-softmmu"
> > > - BUILDMAN="^qemu-riscv64$"
> > > - TOOLCHAIN="riscv"
> > > - name: "test/py qemu-x86"
> > > env:
> > > - TEST_PY_BD="qemu-x86"
> >
> > But why are we removing this? We run all of the rest of the test suites
> > and I don't think this one test adds noticeably to the overall Travis
> > time. Thanks!
>
> The reason was mentioned in the commit message.
>
> As of today there is no pre-built UEFI GRUB image for RISC-V 32/64
> available on the internet, and with travis-ci we don't build GRUB
> images like we do for azure and gitlab.
>
> Do you want to build GRUB image in travis, like what's done in the
> docker image used for azure/gitlab?
But this isn't just for testing GRUB via UEFI, it runs our test/py suite
too. And that's worth doing, right?
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200326/1c1f352f/attachment.sig>
next prev parent reply other threads:[~2020-03-27 2:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 16:05 [PATCH 1/4] travis: Remove qemu-riscv64 testing Bin Meng
2020-03-26 16:05 ` [PATCH 2/4] azure/gitlab: Add qemu-riscv32 testing Bin Meng
2020-03-26 16:05 ` [PATCH 3/4] test/py: Update u_boot_utils.find_ram_base to bypass the low 2MiB memory Bin Meng
2020-03-26 16:05 ` [PATCH 4/4] azure/gitlab: Add RISC-V SPL testing Bin Meng
2020-03-26 16:10 ` [PATCH 1/4] travis: Remove qemu-riscv64 testing Tom Rini
2020-03-27 1:51 ` Bin Meng
2020-03-27 2:01 ` Tom Rini [this message]
2020-03-27 2:19 ` Bin Meng
2020-03-27 2:20 ` Tom Rini
2020-03-27 5:19 ` David Abdurachmanov
2020-03-27 5:31 ` Bin Meng
2020-03-27 5:39 ` David Abdurachmanov
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=20200327020102.GE5793@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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