From: "Liguzinski, WojciechX" <wojciechx.liguzinski@intel.com>
To: Brandon Lo <blo@iol.unh.edu>
Cc: Lincoln Lavoie <lylavoie@iol.unh.edu>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
"David Marchand" <david.marchand@redhat.com>,
"Ajmera, Megha" <megha.ajmera@intel.com>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>,
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: Tue, 30 Nov 2021 07:51:07 +0000 [thread overview]
Message-ID: <BN9PR11MB53727A9BA396B3A6A5DEA56994679@BN9PR11MB5372.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAOeXdvbJ6fahC+sug3CsQhTLYO6aU9NKqZKdbZOOnO7rSANK=g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1549 bytes --]
Ok, thanks Brandon for the tip :)
Let’s see if I can setup the machine with such configuration.
Cheers,
Wojciech
From: Brandon Lo <blo@iol.unh.edu>
Sent: Monday, November 29, 2021 6:58 PM
To: Liguzinski, WojciechX <wojciechx.liguzinski@intel.com>
Cc: Lincoln Lavoie <lylavoie@iol.unh.edu>; Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Thomas Monjalon <thomas@monjalon.net>; David Marchand <david.marchand@redhat.com>; Ajmera, Megha <megha.ajmera@intel.com>; Singh, Jasvinder <jasvinder.singh@intel.com>; dev <dev@dpdk.org>; Aaron Conole <aconole@redhat.com>; Yigit, Ferruh <ferruh.yigit@intel.com>; ci@dpdk.org; Zegota, AnnaX <annax.zegota@intel.com>
Subject: Re: [dpdk-dev] [Bug 826] red_autotest random failures
On Wed, Nov 24, 2021 at 2:48 AM Liguzinski, WojciechX <wojciechx.liguzinski@intel.com<mailto:wojciechx.liguzinski@intel.com>> wrote:
Hi,
Thanks Lincoln, I will also have a try with such script.
Cheers,
Wojciech
Hello Wojciech,
I also recommend trying to run the test with around 4GB of RAM and 2GB of hugepages to see if it fails. That is roughly the number of resources we have per machine that is completely dedicated to unit tests. The amount of RAM available can sometimes increase depending on how many jobs are running per machine, but 4GB is the lowest it can go for the unit test job.
Thanks,
Brandon
--
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu<mailto:blo@iol.unh.edu>
www.iol.unh.edu<http://www.iol.unh.edu>
[-- Attachment #2: Type: text/html, Size: 5152 bytes --]
next prev parent reply other threads:[~2021-11-30 7:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 7:23 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
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 [this message]
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=BN9PR11MB53727A9BA396B3A6A5DEA56994679@BN9PR11MB5372.namprd11.prod.outlook.com \
--to=wojciechx.liguzinski@intel.com \
--cc=aconole@redhat.com \
--cc=annax.zegota@intel.com \
--cc=blo@iol.unh.edu \
--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=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).