From: Thomas Monjalon <thomas@monjalon.net>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
David Marchand <david.marchand@redhat.com>,
Lincoln Lavoie <lylavoie@iol.unh.edu>,
"Ajmera, Megha" <megha.ajmera@intel.com>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>,
"Liguzinski, WojciechX" <wojciechx.liguzinski@intel.com>
Cc: dev <dev@dpdk.org>, Aaron Conole <aconole@redhat.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"ci@dpdk.org" <ci@dpdk.org>,
"Zegota, AnnaX" <annax.zegota@intel.com>
Subject: Re: [dpdk-dev] [Bug 826] red_autotest random failures
Date: Fri, 19 Nov 2021 08:26:16 +0100 [thread overview]
Message-ID: <1928246.j4tpOohVRJ@thomas> (raw)
In-Reply-To: <BN9PR11MB53724D41DC05875D1D7F8E12949B9@BN9PR11MB5372.namprd11.prod.outlook.com>
18/11/2021 23:10, Liguzinski, WojciechX:
> Hi,
>
> I was trying to reproduce this test failure, but for me RED tests are passing.
> I was running the exact test command like the one described in Bug 826 - 'red_autotest' on the current main branch.
The test is not always failing.
There are some failing conditions, please find them.
I think you should try in a container with more limited resources.
next prev parent reply other threads:[~2021-11-19 7:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 7:23 [dpdk-dev] [Bug 826] red_autotest random failures bugzilla
2021-11-12 13:51 ` David Marchand
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 [this message]
2021-11-19 16:53 ` Dumitrescu, Cristian
2021-11-19 17:25 ` Lincoln Lavoie
2021-11-24 7:48 ` Liguzinski, WojciechX
2021-11-29 17:58 ` Brandon Lo
2021-11-30 7:51 ` Liguzinski, WojciechX
2021-12-10 13:31 ` Liguzinski, WojciechX
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=1928246.j4tpOohVRJ@thomas \
--to=thomas@monjalon.net \
--cc=aconole@redhat.com \
--cc=annax.zegota@intel.com \
--cc=ci@dpdk.org \
--cc=cristian.dumitrescu@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jasvinder.singh@intel.com \
--cc=lylavoie@iol.unh.edu \
--cc=megha.ajmera@intel.com \
--cc=wojciechx.liguzinski@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.