From: David Christensen <drc@linux.vnet.ibm.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] autotest: disable lcores_autotest on ppc
Date: Tue, 27 Apr 2021 11:14:07 -0700 [thread overview]
Message-ID: <025c64c7-16bd-d3bc-7688-1df26db13aac@linux.vnet.ibm.com> (raw)
In-Reply-To: <20210420114508.397249-1-luca.boccassi@gmail.com>
On 4/20/21 4:45 AM, luca.boccassi@gmail.com wrote:
> From: Luca Boccassi <luca.boccassi@microsoft.com>
>
> This test consistently times out on ppc64 builds. Disable it.
>
> Cc: stable@dpdk.org
>
> Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com>
Is there something new about how/when this test is run during continuous
integration? The test time is dependent on the value of RTE_MAX_LCORE
which is currently 1536. When I run the test locally it takes around 50
seconds to complete and completes without errors. If I reduce the value
down to 128 the test completes in around 5 seconds. The current value
has been in the code for nearly 2 years so I'm curious why the sudden
change in CI results.
We could could reduce the default value for RTE_MAX_LCORE (I don't often
have access to a system that actually has this many cores) or we could
skip the test in this situation as well.
Dave
next prev parent reply other threads:[~2021-04-27 18:14 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
2021-04-27 17:38 ` David Christensen
2021-04-27 18:14 ` David Christensen [this message]
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=025c64c7-16bd-d3bc-7688-1df26db13aac@linux.vnet.ibm.com \
--to=drc@linux.vnet.ibm.com \
--cc=dev@dpdk.org \
/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).