DPDK CI discussions
 help / color / mirror / Atom feed
From: "Danilewicz, MarcinX" <marcinx.danilewicz@intel.com>
To: Brandon Lo <blo@iol.unh.edu>, Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
	"Ajmera, Megha" <megha.ajmera@intel.com>,
	"Singh, Jasvinder" <jasvinder.singh@intel.com>,
	"Zegota, AnnaX" <annax.zegota@intel.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>,
	"ci@dpdk.org" <ci@dpdk.org>
Subject: RE: [dpdk-dev] [Bug 826] red_autotest random failures
Date: Thu, 3 Feb 2022 23:31:44 +0000
Message-ID: <BY5PR11MB3926B51474212BE75687EFE68F289@BY5PR11MB3926.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BY5PR11MB3926834037373B9E80AC09C88F279@BY5PR11MB3926.namprd11.prod.outlook.com>

Hi Brandon,

It looks like I am searching for some local script/s to generate VM? Or something for VM..?

It started from this message:
Step 11/12 : COPY scripts /scripts
COPY failed: file not found in build context or excluded by .dockerignore: stat scripts: file does not exist

I'll start searching for this, but perhaps you can enlighten me what is that and where it may be found. If possible 😊


Kind Regards,
/Marcin

-----Original Message-----
From: Danilewicz, MarcinX 
Sent: Wednesday, February 2, 2022 6:08 PM
To: Brandon Lo <blo@iol.unh.edu>; Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Ajmera, Megha <megha.ajmera@intel.com>; Singh, Jasvinder <jasvinder.singh@intel.com>; Zegota, AnnaX <annax.zegota@intel.com>; Yigit, Ferruh <ferruh.yigit@intel.com>; thomas@monjalon.net; david.marchand@redhat.com; ci@dpdk.org
Subject: RE: [dpdk-dev] [Bug 826] red_autotest random failures

Hi Brandon,

I'll will look into this config file to see what I can do about it 😊


" a specific amount of resources (4GB RAM, 2 cores) to each container, so that can be another factor that affects the frequency of these failures.

If this issue seems too dependent on the current system load and other situational factors, it might be good to think about running the red_autotest separate from other tests in the lab so it does not have to compete for resources.
Any thoughts on this?"

CPU family might be important, from CPU features perspective.  Previously some throughput  tests I was executing using two different machines (different core families) to get correct (expected) results. Perhaps nothing has changed since then.

I'll let you know about my findings with that docker based installation.


Kind Regards,
/Marcin
--------------------------------------------------------------
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263


This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.

  reply	other threads:[~2022-02-03 23:31 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
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 [this message]
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=BY5PR11MB3926B51474212BE75687EFE68F289@BY5PR11MB3926.namprd11.prod.outlook.com \
    --to=marcinx.danilewicz@intel.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=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

DPDK CI discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \
		ci@dpdk.org
	public-inbox-index ci

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.ci


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git