From: Thomas Monjalon <thomas@monjalon.net>
To: honnappa.nagarahalli@arm.com, david.marchand@redhat.com,
ruifeng.wang@arm.com, Aaron Conole <aconole@redhat.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ci: remove aarch64 from Travis jobs
Date: Thu, 25 Mar 2021 18:11:58 +0100 [thread overview]
Message-ID: <7406412.c1iilDCem9@thomas> (raw)
In-Reply-To: <f7tlfab191z.fsf@dhcp-25.97.bos.redhat.com>
25/03/2021 17:40, Aaron Conole:
> 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 managed without applying this patch.
> >
> > After one year passed, what is the situation today regarding Travis?
> > Can we rely on Travis service?
>
> So far, yes.
>
> > For which workload? Which architecture?
>
> I think for all of them. Looking at even the failures which pop up for
> the latest patches, they seem like real failures.
>
> ex:
> https://travis-ci.com/github/ovsrobot/dpdk/jobs/493722400
> https://travis-ci.com/github/ovsrobot/dpdk/jobs/493688879
> https://travis-ci.com/github/ovsrobot/dpdk/jobs/493624012
> https://travis-ci.com/github/ovsrobot/dpdk/jobs/493611597
>
> These are ABI, and doc failures - different arches, etc.
>
> Seems like it's quite usable.
>
> > Aaron, what do you recommend?
>
> I think we should drop this patch - Travis continues to be useful even
> for individual developers checking their own results. It seems the
> service works quite a bit better now for the project as well, thanks to
> Honnappa and other ARM folks for working with them.
Thanks all, patch classified as "Rejected".
prev parent reply other threads:[~2021-03-25 17:12 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
2021-03-25 15:46 ` Thomas Monjalon
2021-03-25 16:40 ` Aaron Conole
2021-03-25 17:11 ` Thomas Monjalon [this message]
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=7406412.c1iilDCem9@thomas \
--to=thomas@monjalon.net \
--cc=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=ruifeng.wang@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).