From: dwilder <dwilder@us.ibm.com>
To: Aaron Conole <aconole@redhat.com>
Cc: David Christensen <drc@linux.vnet.ibm.com>, ci@dpdk.org
Subject: Re: [dpdk-ci] [DISCUSS] DPDK PPC testing / CI
Date: Tue, 05 May 2020 09:43:35 -0700 [thread overview]
Message-ID: <3dcdd2d736ddfae887c033c2168c8f29@linux.vnet.ibm.com> (raw)
In-Reply-To: <f7t4ksubh8c.fsf@dhcp-25.97.bos.redhat.com>
On 2020-05-05 07:15, Aaron Conole wrote:
> Hello David(s),
>
> I know you are keen on having PPC support in the DPDK CI. Right now,
> we're seeing serious reliability problems with Travis for the ARM
> support (and even Intel has been slightly misbehaving). We're not sure
> whether the same issues exist under PPC. How extensive have you tested
> with the PPC series and support under Travis CI?
>
> Just starting the conversation right now.
>
> -Aaron
Hi Aaron
I had been running the dpdk ci daily, however only a few runs last month
as I have been distracted.
I have see transient failures I attribute to the travis infrastructure
issue, things like failure to install dependencies or out of space
issues. The out of space problems I have only seen on ppc and arm.
Dave
prev parent reply other threads:[~2020-05-05 16:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 14:15 Aaron Conole
2020-05-05 16:43 ` dwilder [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=3dcdd2d736ddfae887c033c2168c8f29@linux.vnet.ibm.com \
--to=dwilder@us.ibm.com \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=drc@linux.vnet.ibm.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).