All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>,
	Jerin Jacob <jerinjacobk@gmail.com>
Cc: David Marchand <david.marchand@redhat.com>,
	dpdklab <dpdklab@iol.unh.edu>, dev <dev@dpdk.org>,
	ci@dpdk.org, Aaron Conole <aconole@redhat.com>,
	David Hunt <david.hunt@intel.com>
Subject: Re: [dpdk-dev] [dpdklab] Re: distributor test failure in UNH CI on ARM
Date: Tue, 19 Jan 2021 05:02:23 +0100	[thread overview]
Message-ID: <04c826d3-d365-4abb-d5a9-24c1e94626ec@partner.samsung.com> (raw)
In-Reply-To: <CAOE1vsOehF4ZMOWffpEv=QF6YOc5wXtg23PV83B9CLiTMn8wQA@mail.gmail.com>

Hi All,

I was finally able to reproduce the issue, but on x86_64 machine with 32 
cores.

You can find a patch fixing it here:
https://inbox.dpdk.org/dev/20210119035910.8324-1-l.wojciechow@partner.samsung.com/T/#t


Best regards

Lukasz


W dniu 11.01.2021 o 15:19, Lincoln Lavoie pisze:
> Hi Jerin,
>
> There is a process for this defined.  A maintainer should open a BUG 
> for the CI lab, requesting specific tests or test cases be disabled, 
> as it's a known failure being worked on. Once the test is disabled, 
> the bug will be updated / assigned back to the maintainer, and should 
> not be closed until the issue is fixed and the test can be 
> re-enabled.  This is so we don't lose track of anything.
>
> Cheers,
> Lincoln
>
> On Mon, Jan 11, 2021 at 9:05 AM Jerin Jacob <jerinjacobk@gmail.com 
> <mailto:jerinjacobk@gmail.com>> wrote:
>
>
>
>     On Mon, Jan 11, 2021 at 7:28 PM Lincoln Lavoie
>     <lylavoie@iol.unh.edu <mailto:lylavoie@iol.unh.edu>> wrote:
>
>         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)?
>
>
>
>     Maybe it is better to have a "known issue" based skip mechanism to
>     address this in CI.
>
>
>         Cheers,
>         LIncoln
>
>         On Mon, Jan 11, 2021 at 8:54 AM Jerin Jacob
>         <jerinjacobk@gmail.com <mailto:jerinjacobk@gmail.com>> wrote:
>
>             On Mon, Jan 11, 2021 at 6:38 PM David Marchand
>             <david.marchand@redhat.com
>             <mailto:david.marchand@redhat.com>> wrote:
>             >
>             > Hey guys,
>             >
>             > On Mon, Jan 11, 2021 at 9:14 AM David Marchand
>             > <david.marchand@redhat.com
>             <mailto: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/
>             <https://protect2.fireeye.com/v1/url?k=8a9fba02-d504834f-8a9e314d-0cc47aa8f5ba-6a770aebaf9cc635&q=1&e=342f3a9f-26e9-459f-b456-e4c0f24f9551&u=https%3A%2F%2Flab.dpdk.org%2Fresults%2Fdashboard%2Fpatchsets%2F15077%2F>
>             > >
>             > > 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 <mailto:lylavoie@iol.unh.edu>
>         https://www.iol.unh.edu
>         <https://protect2.fireeye.com/v1/url?k=02515c2d-5dca6560-0250d762-0cc47aa8f5ba-f4d7765d9763c114&q=1&e=342f3a9f-26e9-459f-b456-e4c0f24f9551&u=https%3A%2F%2Fwww.iol.unh.edu%2F>
>         +1-603-674-2755 (m)
>         <https://protect2.fireeye.com/v1/url?k=75833b33-2a18027e-7582b07c-0cc47aa8f5ba-f87ac679cb8c13d6&q=1&e=342f3a9f-26e9-459f-b456-e4c0f24f9551&u=https%3A%2F%2Fwww.iol.unh.edu%2F>
>
>
>
> -- 
> *Lincoln Lavoie*
> Senior Engineer, Broadband Technologies
> 21 Madbury Rd., Ste. 100, Durham, NH 03824
> lylavoie@iol.unh.edu <mailto:lylavoie@iol.unh.edu>
> https://www.iol.unh.edu 
> <https://protect2.fireeye.com/v1/url?k=b09c268b-ef071fc6-b09dadc4-0cc47aa8f5ba-8682c86b1454963d&q=1&e=342f3a9f-26e9-459f-b456-e4c0f24f9551&u=https%3A%2F%2Fwww.iol.unh.edu%2F>
> +1-603-674-2755 (m)
> <https://protect2.fireeye.com/v1/url?k=75edce14-2a76f759-75ec455b-0cc47aa8f5ba-ef8e65dee33787c3&q=1&e=342f3a9f-26e9-459f-b456-e4c0f24f9551&u=https%3A%2F%2Fwww.iol.unh.edu%2F>

-- 
Lukasz Wojciechowski
Principal Software Engineer

Samsung R&D Institute Poland
Samsung Electronics
Office +48 22 377 88 25
l.wojciechow@partner.samsung.com


      reply	other threads:[~2021-01-19  4:02 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-dev] distributor test failure in UNH CI on ARM 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     ` Jerin Jacob
2021-01-11 13:56       ` Lincoln Lavoie
2021-01-11 14:04         ` Jerin Jacob
2021-01-11 14:19           ` [dpdk-dev] [dpdklab] " Lincoln Lavoie
2021-01-19  4:02             ` Lukasz Wojciechowski [this message]

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=04c826d3-d365-4abb-d5a9-24c1e94626ec@partner.samsung.com \
    --to=l.wojciechow@partner.samsung.com \
    --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=lylavoie@iol.unh.edu \
    /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.