All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: dpdklab <dpdklab@iol.unh.edu>, Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: 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-dev] distributor test failure in UNH CI on ARM
Date: Mon, 11 Jan 2021 14:08:09 +0100	[thread overview]
Message-ID: <CAJFAV8zdZZAjM2O46iFLmKZWnYJX1hoQ5r=sB0Rn=bu4qU-M5w@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8wun5ec_mWHz_5cxLw=PpgApragNxtVK=gP1gZ7YDLRQw@mail.gmail.com>

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?



-- 
David Marchand


  parent reply	other threads:[~2021-01-11 13:08 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 [this message]
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

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