DPDK CI discussions
 help / color / mirror / Atom feed
From: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>,
	David Marchand <david.marchand@redhat.com>,
	"Tu, Lijuan" <lijuan.tu@intel.com>
Cc: sys_stv <sys_stv@intel.com>, "ci@dpdk.org" <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: Wed, 22 Sep 2021 06:17:52 +0000	[thread overview]
Message-ID: <64221AA6-3141-4411-A5D4-65251507A2E4@intel.com> (raw)
In-Reply-To: <CAOE1vsN7m2UXY7tSM5aNqRvKQ32CbLSPEaMrvSyM7X2M8ANH5Q@mail.gmail.com>

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

Thanks Lincoln and David to reminder.

Actually, this is a real issue on main branch.

The pf_smoke failed due to dpdk bad commit id: b3d95f1817288ca228f09b9164d6d3ff6249b175(has been merged into main branch).
Currently, its fixed patch(http://patches.dpdk.org/project/dpdk/list/?series=18963) are provided by Dev and tested passed by CI, but not merged into main branch due to share code limitation.
Test report: [dpdk-test-report] (Testing) |SUCCESS| pw(98992-98993) sid(18963) job(PER_PATCH_BUILD7871) [v2, 2/2] net/iavf: remove support for IP fragment default RSS<http://mails.dpdk.org/archives/test-report/2021-September/220075.html>)

I don’t know when the hotfix patch could be merged. Before that, shall CI be disabled for this real issue?


From: Lincoln Lavoie <lylavoie@iol.unh.edu>
Date: Tuesday, September 21, 2021 at 21:22
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" <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

Hi All,

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


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

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.


David Marchand

Lincoln Lavoie
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
+1-603-674-2755 (m)
[Image removed by sender.]<https://www.iol.unh.edu/>

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

  reply	other threads:[~2021-09-22  6:18 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
2021-09-22  6:17   ` Chen, Zhaoyan [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=64221AA6-3141-4411-A5D4-65251507A2E4@intel.com \
    --to=zhaoyan.chen@intel.com \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=ferruh.yigit@intel.com \
    --cc=lijuan.tu@intel.com \
    --cc=lylavoie@iol.unh.edu \
    --cc=sys_stv@intel.com \
    --cc=thomas@monjalon.net \


* 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).