From: Jerin Jacob <jerinjacobk@gmail.com>
To: Aaron Conole <aconole@redhat.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>,
David Marchand <david.marchand@redhat.com>,
"Ruifeng Wang (Arm Technology China)" <ruifeng.wang@arm.com>,
Gavin Hu <gavin.hu@arm.com>,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
Michael Santana <maicolgabriel@hotmail.com>
Subject: Re: [dpdk-dev] [PATCH] ci: remove aarch64 from Travis jobs
Date: Thu, 16 Apr 2020 19:00:47 +0530 [thread overview]
Message-ID: <CALBAE1NCTuc2YrZLN77g26gV5v-gv8vwKTQe_kk4DWmM-n+3Rg@mail.gmail.com> (raw)
In-Reply-To: <f7timhz4n30.fsf@dhcp-25.97.bos.redhat.com>
On Thu, Apr 16, 2020 at 6:14 PM Aaron Conole <aconole@redhat.com> wrote:
>
> Thomas Monjalon <thomas@monjalon.net> writes:
>
> > Travis is not reliable for native Arm and PPC:
> > https://travis-ci.community/t/disk-quota-exceeded-on-arm64/7619/6
> >
> > In order to get reliable Travis reports,
> > the use of Arm machines is removed until Travis fixes it.
> >
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > ---
>
> We should add back the cross-build if we do this - at least then we
> could have a reliable compilation test of Arm64 code. Does it make
> sense?
+1
>
next prev parent reply other threads:[~2020-04-16 13:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 11:00 Thomas Monjalon
2020-04-16 12:44 ` Aaron Conole
2020-04-16 13:30 ` Jerin Jacob [this message]
2020-04-16 13:43 ` David Marchand
2020-04-16 13:45 ` Aaron Conole
2020-04-16 14:39 ` Thomas Monjalon
2020-04-16 15:55 ` Honnappa Nagarahalli
2020-04-16 17:08 ` Aaron Conole
2020-04-19 8:01 ` David Marchand
2020-04-20 15:35 ` Ruifeng Wang
2020-04-16 17:07 ` Aaron Conole
2020-04-17 8:49 ` Ruifeng Wang
2020-04-17 10:09 ` Thomas Monjalon
2021-03-25 15:46 ` Thomas Monjalon
2021-03-25 16:40 ` Aaron Conole
2021-03-25 17:11 ` Thomas Monjalon
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=CALBAE1NCTuc2YrZLN77g26gV5v-gv8vwKTQe_kk4DWmM-n+3Rg@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=maicolgabriel@hotmail.com \
--cc=ruifeng.wang@arm.com \
--cc=thomas@monjalon.net \
/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).