DPDK CI discussions
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: "Danilewicz, MarcinX" <marcinx.danilewicz@intel.com>
Cc: Lincoln Lavoie <lylavoie@iol.unh.edu>,
	 "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 19:11:00 -0500	[thread overview]
Message-ID: <CAOeXdvY_KQ0U0CMjsLZu74NX8id5VVTMuKhBE1vatNTrij1i2Q@mail.gmail.com> (raw)
In-Reply-To: <BY5PR11MB3926B51474212BE75687EFE68F289@BY5PR11MB3926.namprd11.prod.outlook.com>

On Thu, Feb 3, 2022 at 6:31 PM Danilewicz, MarcinX
<marcinx.danilewicz@intel.com> wrote:
>
> 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 😊

Hi Marcin,

Sorry about that. You can probably remove that line from the
Dockerfile. It is used to copy short bash scripts that run meson/ninja
with DPDK.
For unit testing, we run a small bash script like this:

#!/bin/bash
tar xzfm dpdk.tar.gz
cd dpdk
meson build --werror
ninja -C build install
cd build
meson test --suite fast-tests -t 60

Thanks,
Brandon


-- 
Brandon Lo
UNH InterOperability Laboratory
21 Madbury Rd, Suite 100, Durham, NH 03824
blo@iol.unh.edu
www.iol.unh.edu

  reply	other threads:[~2022-02-04  0:11 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
2022-02-04  0:11                                     ` Brandon Lo [this message]
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=CAOeXdvY_KQ0U0CMjsLZu74NX8id5VVTMuKhBE1vatNTrij1i2Q@mail.gmail.com \
    --to=blo@iol.unh.edu \
    --cc=annax.zegota@intel.com \
    --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=marcinx.danilewicz@intel.com \
    --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).