From: David Marchand <david.marchand@redhat.com>
To: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Cc: 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 14:51:59 +0100 [thread overview]
Message-ID: <CAJFAV8yKFudYdKX+gYjxYAHpB=0kBD88My2YX9NhiJvzLesMeA@mail.gmail.com> (raw)
In-Reply-To: <bug-826-3@http.bugs.dpdk.org/>
On Fri, Oct 8, 2021 at 9:24 AM <bugzilla@dpdk.org> wrote:
>
> https://bugs.dpdk.org/show_bug.cgi?id=826
>
> Bug ID: 826
> Summary: red_autotest random failures
> Product: DPDK
> Version: unspecified
> Hardware: All
> OS: All
> Status: UNCONFIRMED
> Severity: normal
> Priority: Normal
> Component: other
> Assignee: cristian.dumitrescu@intel.com
> Reporter: david.marchand@redhat.com
> CC: dev@dpdk.org, jasvinder.singh@intel.com
> Target Milestone: ---
>
> A recent failure can be found at:
> https://lab.dpdk.org/results/dashboard/patchsets/19223/
>
> 50/94 DPDK:fast-tests / red_autotest FAIL 0.86s
> exit status 1
functional test 6 : use several queues (each with its own run-time data),
use several RED configurations (such that each
configuration is sharte_red by multiple queues),
increase average queue size to target level,
dequeue all packets until queue is empty,
confirm that average queue size is computed correctly
while queue is empty
(this is a larger scale version of functional test 3)
queue config q avg before q avg after expected
difference % tolerance % result
0 0 1022.0000 1022.0000 1016.0627
0.5843 5.0000 pass
1 0 1022.0000 1022.0000 1016.0627
0.5843 5.0000 pass
2 1 1022.0000 1022.0000 1010.1483
1.1733 5.0000 pass
3 1 1022.0000 937.1660 1010.1483
7.2249 5.0000 fail
-------------------------------------<fail>-------------------------------------
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
next parent reply other threads:[~2021-11-12 13:52 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 [this message]
2021-11-12 14:10 ` Lincoln Lavoie
2021-11-12 14:15 ` David Marchand
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='CAJFAV8yKFudYdKX+gYjxYAHpB=0kBD88My2YX9NhiJvzLesMeA@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=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).