DPDK CI discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>,
	"Tu, Lijuan" <lijuan.tu@intel.com>,
	"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Cc: sys_stv <sys_stv@intel.com>,
	ci@dpdk.org, Aaron Conole <aconole@redhat.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-ci] Failing pf_smoke test
Date: Tue, 21 Sep 2021 09:20:46 -0400	[thread overview]
Message-ID: <CAOE1vsN7m2UXY7tSM5aNqRvKQ32CbLSPEaMrvSyM7X2M8ANH5Q@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8z3Ez1JoumFVu4nkUntSX_C+VBQS=jSPH1ht0TC3dPscg@mail.gmail.com>

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

Hi All,

This is a failing test in the Intel Lab.  Zhaoyan and Lijuan, can you check
on the status of that test case?

Cheers,
Lincoln

On Tue, Sep 21, 2021 at 9:12 AM David Marchand <david.marchand@redhat.com>
wrote:

> Hello,
>
> For a couple of weeks (first report for me on 09/07), I receive
> failure reports for the pf_smoke / test_pf_rss test case on any patch
> I post.
>
> Can this be fixed?
> Else, please disable this test.
>
>
> Thanks.
>
> --
> David Marchand
>
>

-- 
*Lincoln Lavoie*
Principal 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: 1977 bytes --]

  reply	other threads:[~2021-09-21 13:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21 13:12 David Marchand
2021-09-21 13:20 ` Lincoln Lavoie [this message]
2021-09-22  6:17   ` Chen, Zhaoyan
2021-09-22  7:23     ` Thomas Monjalon
2021-09-22  9:12       ` Chen, Zhaoyan
2021-09-22  9:52       ` David Marchand
2021-09-22 10:02         ` Thomas Monjalon
2021-09-30  7:58     ` David Marchand

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=CAOE1vsN7m2UXY7tSM5aNqRvKQ32CbLSPEaMrvSyM7X2M8ANH5Q@mail.gmail.com \
    --to=lylavoie@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=ferruh.yigit@intel.com \
    --cc=lijuan.tu@intel.com \
    --cc=sys_stv@intel.com \
    --cc=thomas@monjalon.net \
    --cc=zhaoyan.chen@intel.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).