From: David Marchand <david.marchand@redhat.com>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
dev <dev@dpdk.org>, Aaron Conole <aconole@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
ci@dpdk.org
Subject: Re: [dpdk-dev] [Bug 826] red_autotest random failures
Date: Fri, 12 Nov 2021 15:15:36 +0100 [thread overview]
Message-ID: <CAJFAV8xyTthDwd92Su0=8yzAFuodW2pag8F3rou658wj7H=X-w@mail.gmail.com> (raw)
In-Reply-To: <CAOE1vsOSG=cR726c-DAh1+D5GPWu3hRWYm8TJnzVw2pMZS5kJQ@mail.gmail.com>
On Fri, Nov 12, 2021 at 3:11 PM Lincoln Lavoie <lylavoie@iol.unh.edu> wrote:
>> This failure keeps on popping in the CI.
>> The bug report is one month old, with no reply.
>>
>>
>> I sent a proposal of removing red_autotest from the list executed by the CI.
>> https://patchwork.dpdk.org/project/dpdk/patch/20211027140458.2502-2-david.marchand@redhat.com/
>>
>> It might be the best solution waiting for an analysis.
>>
>>
>> --
>> David Marchand
>>
>
> Hi David,
>
> My understanding is, removing the test would require removing it from the DPDK unit tests, we are just running the fast-tests suite for the unit tests. DPDK's unit test structure / framework does not allow removing or customizing the suite of tests beyond the suites.
https://patchwork.dpdk.org/project/dpdk/patch/20211027140458.2502-2-david.marchand@redhat.com/
>
> In the lab, Brandon has been looking into and trying different configurations for running the tests within the containers along the lines of the CPU pinning requirements that might be assumed by the unit tests. So far, everything he has tried has still had the similar failures / issues. We are still looking into it, so the bug is not sitting without action, just no final resolution.
The mail I sent was not a comment for the investigation on UNH side.
The ask is for Cristian to have a look too.
--
David Marchand
next prev parent reply other threads:[~2021-11-12 14:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-826-3@http.bugs.dpdk.org/>
2021-11-12 13:51 ` David Marchand
2021-11-12 14:10 ` Lincoln Lavoie
2021-11-12 14:15 ` David Marchand [this message]
2021-11-15 11:51 ` Dumitrescu, Cristian
2021-11-15 17:26 ` Liguzinski, WojciechX
2021-11-18 22:10 ` Liguzinski, WojciechX
2021-11-19 7:26 ` Thomas Monjalon
2021-11-19 16:53 ` Dumitrescu, Cristian
2021-11-19 17:25 ` Lincoln Lavoie
[not found] ` <BN9PR11MB53729251C262EEBB1134A61194619@BN9PR11MB5372.namprd11.prod.outlook.com>
2021-11-29 17:58 ` Brandon Lo
2021-11-30 7:51 ` Liguzinski, WojciechX
2021-12-10 13:31 ` Liguzinski, WojciechX
[not found] ` <SA0PR11MB46708D32B6B2EC31D3DCE17F975A9@SA0PR11MB4670.namprd11.prod.outlook.com>
[not found] ` <BY5PR11MB3926999DD139D10AD76D177F8F5B9@BY5PR11MB3926.namprd11.prod.outlook.com>
[not found] ` <BY5PR11MB39261E9379E18C67BB4FB9938F5B9@BY5PR11MB3926.namprd11.prod.outlook.com>
[not found] ` <BY5PR11MB3926DF1466F5815D5D2FEC798F259@BY5PR11MB3926.namprd11.prod.outlook.com>
[not found] ` <CAOE1vsPcKAiTMPGH1VYwoTccWi7b=9DJdObdPJZhKQvqNQsFmw@mail.gmail.com>
2022-02-02 14:51 ` Brandon Lo
2022-02-02 17:07 ` Danilewicz, MarcinX
2022-02-03 23:31 ` Danilewicz, MarcinX
2022-02-04 0:11 ` Brandon Lo
2022-03-09 10:01 ` Danilewicz, MarcinX
2022-03-09 14:48 ` Brandon Lo
2022-03-10 17:25 ` Danilewicz, MarcinX
2021-11-22 8:17 ` David Marchand
2021-11-22 13:34 ` Lincoln Lavoie
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='CAJFAV8xyTthDwd92Su0=8yzAFuodW2pag8F3rou658wj7H=X-w@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=lylavoie@iol.unh.edu \
--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).