From: Luca Boccassi <luca.boccassi@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, david.marchand@redhat.com,
David Christensen <drc@linux.vnet.ibm.com>
Subject: Re: [dpdk-dev] [PATCH] autotest: disable lcores_autotest on ppc
Date: Thu, 22 Apr 2021 14:45:22 +0100 [thread overview]
Message-ID: <bf944af57ba20042821056d2bc2a5b6f8e92e9a6.camel@gmail.com> (raw)
In-Reply-To: <3057614.rWQXVndaHx@thomas>
On Thu, 2021-04-22 at 14:43 +0200, Thomas Monjalon wrote:
> 22/04/2021 14:36, Luca Boccassi:
> > On Thu, 2021-04-22 at 13:01 +0200, Thomas Monjalon wrote:
> > > 22/04/2021 12:26, Luca Boccassi:
> > > > On Wed, 2021-04-21 at 17:06 +0200, Thomas Monjalon wrote:
> > > > > 20/04/2021 13:45, luca.boccassi@gmail.com:
> > > > > > This test consistently times out on ppc64 builds. Disable it.
> > > > >
> > > > > It looks like hiding an issue.
> > > > > Is there any specific reason for this timeout?
> > > >
> > > > As mentioned in the message, there's nothing useful in the logs, it
> > > > just times out.
> > >
> > > OK but it could be fixed probably instead of disabling.
> >
> > I'm sure it could, and it would be great if somebody would do so - but
> > I do not have either the time or the hardware to take care of
> > PPC-specific problems, apart from the bare minimum to remove blockers
> > to get things done for Debian 11.
>
> First things first, let's Cc the PPC maintainer:
> David Christensen <drc@linux.vnet.ibm.com>
https://bugs.dpdk.org/show_bug.cgi?id=684
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2021-04-22 13:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 11:45 luca.boccassi
2021-04-21 15:06 ` Thomas Monjalon
2021-04-22 10:26 ` Luca Boccassi
2021-04-22 11:01 ` Thomas Monjalon
2021-04-22 12:36 ` Luca Boccassi
2021-04-22 12:43 ` Thomas Monjalon
2021-04-22 13:45 ` Luca Boccassi [this message]
2021-04-27 17:38 ` David Christensen
2021-04-27 18:14 ` David Christensen
2021-04-28 19:36 ` David Christensen
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=bf944af57ba20042821056d2bc2a5b6f8e92e9a6.camel@gmail.com \
--to=luca.boccassi@gmail.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.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).