DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: Jerin Jacob <jerinjacobk@gmail.com>
Cc: David Marchand <david.marchand@redhat.com>,
	dpdklab <dpdklab@iol.unh.edu>, dev <dev@dpdk.org>,
	 ci@dpdk.org,
	Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>,
	 Aaron Conole <aconole@redhat.com>,
	David Hunt <david.hunt@intel.com>
Subject: Re: [dpdk-ci] [dpdk-dev] distributor test failure in UNH CI on ARM
Date: Mon, 11 Jan 2021 08:56:20 -0500	[thread overview]
Message-ID: <CAOE1vsOd5fEy9x2i2Do8CbPY6r7tb4=agxgkWY45JxgnN_j18Q@mail.gmail.com> (raw)
In-Reply-To: <CALBAE1M9CAeQdvEhESgH7iauHqfHBO6wsun8MOVk1Z7M3XuWfw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1514 bytes --]

Hi All,

How do you want us to handle this in the lab?  Can we pull / disable this
unit test from the arm system, ignore it from now (if it's going to be
fixed), disable the unit tests on arm for now (while it's being fixed)?

Cheers,
LIncoln

On Mon, Jan 11, 2021 at 8:54 AM Jerin Jacob <jerinjacobk@gmail.com> wrote:

> On Mon, Jan 11, 2021 at 6:38 PM David Marchand
> <david.marchand@redhat.com> wrote:
> >
> > Hey guys,
> >
> > On Mon, Jan 11, 2021 at 9:14 AM David Marchand
> > <david.marchand@redhat.com> wrote:
> > > UNH CI is raising failures on a ARM server for the distributor test:
> > > https://lab.dpdk.org/results/dashboard/patchsets/15077/
> > >
> > > Worker 59 handled 0 packets
> > > Worker 60 handled 0 packets
> > > Worker 61 handled 0 packets
> > > Worker 62 handled 0 packets
> > > Sanity test with non-zero hashes done
> > > === testing big burst (burst) ===
> > > line 258: Missing packets, expected 783
> > > Test Failed
> > > RTE>>
> > > --- stderr ---
> >
> > Looking at the dashboard, I did not see a passing instance of this
> > unit test for ARM.
> > Did it ever work?
>
> No. There are a lot of sync barriers are missing in the distributor
> library.
> Since evendev is kind of replacing this library, we made the fix as
> low priority.
>
>
>
> >
> >
> >
> > --
> > David Marchand
> >
>


-- 
*Lincoln Lavoie*
Senior Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>

[-- Attachment #2: Type: text/html, Size: 3248 bytes --]

  reply	other threads:[~2021-01-11 13:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210111081428eucas1p1f5f234cef3e3582ab8ba2726d8d105ea@eucas1p1.samsung.com>
2021-01-11  8:14 ` [dpdk-ci] " David Marchand
2021-01-11 10:37   ` Lukasz Wojciechowski
2021-01-11 13:04     ` David Marchand
2021-01-11 13:08   ` David Marchand
2021-01-11 13:54     ` [dpdk-ci] [dpdk-dev] " Jerin Jacob
2021-01-11 13:56       ` Lincoln Lavoie [this message]
2021-01-11 14:04         ` Jerin Jacob
2021-01-11 14:19           ` [dpdk-ci] [dpdklab] " Lincoln Lavoie
2021-01-19  4:02             ` Lukasz Wojciechowski

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='CAOE1vsOd5fEy9x2i2Do8CbPY6r7tb4=agxgkWY45JxgnN_j18Q@mail.gmail.com' \
    --to=lylavoie@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=david.hunt@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    --cc=jerinjacobk@gmail.com \
    --cc=l.wojciechow@partner.samsung.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 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).