From: Thomas Monjalon <thomas@monjalon.net>
To: Aaron Conole <aconole@redhat.com>, Ruifeng Wang <Ruifeng.Wang@arm.com>
Cc: David Marchand <david.marchand@redhat.com>, dev <dev@dpdk.org>,
Gavin Hu <Gavin.Hu@arm.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
Michael Santana <maicolgabriel@hotmail.com>, nd <nd@arm.com>,
honnappa.nagarahalli@arm.com
Subject: Re: [dpdk-dev] [PATCH] ci: remove aarch64 from Travis jobs
Date: Fri, 17 Apr 2020 12:09:51 +0200 [thread overview]
Message-ID: <3628048.OYXXYNVTWy@thomas> (raw)
In-Reply-To: <HE1PR0801MB202569878793FBC570F972829ED90@HE1PR0801MB2025.eurprd08.prod.outlook.com>
17/04/2020 10:49, Ruifeng Wang:
> From: Thomas Monjalon <thomas@monjalon.net>
> > 16/04/2020 15:45, Aaron Conole:
> > > David Marchand <david.marchand@redhat.com> writes:
> > > > On Thu, Apr 16, 2020 at 2:44 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?
> > > >
> > > > I don't see them removed by this patch, the two jobs are still present ?
> > >
> > > Whoops - for some reason I missed them. Nevermind :)
> >
> > So? Acked?
> >
> Can we achieve this by allowing failures on AArch64 jobs?
> https://docs.travis-ci.com/user/build-matrix/#rows-that-are-allowed-to-fail
>
> Add following setting:
> jobs:
> allow_failures:
> - arch: arm64
>
> So we can keep the jobs while not suffering from unstable infrastructure.
> Results of these jobs will still observable. This gives us a chance to know when jobs are stable.
I don't see the benefit. It will just make Travis reports unclear.
I wait at least one more week to give Travis a chance to fix Arm support.
Please work with them.
If no result shortly, I will apply this patch to improve DPDK CI reliability.
next prev parent reply other threads:[~2020-04-17 10:09 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
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 [this message]
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=3628048.OYXXYNVTWy@thomas \
--to=thomas@monjalon.net \
--cc=Gavin.Hu@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=maicolgabriel@hotmail.com \
--cc=nd@arm.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 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).