From: Thomas Monjalon <thomas@monjalon.net>
To: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Cc: Lincoln Lavoie <lylavoie@iol.unh.edu>,
David Marchand <david.marchand@redhat.com>,
"Tu, Lijuan" <lijuan.tu@intel.com>, sys_stv <sys_stv@intel.com>,
"ci@dpdk.org" <ci@dpdk.org>, Aaron Conole <aconole@redhat.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-ci] Failing pf_smoke test
Date: Wed, 22 Sep 2021 09:23:00 +0200 [thread overview]
Message-ID: <2731761.8huRqIiH2e@thomas> (raw)
In-Reply-To: <64221AA6-3141-4411-A5D4-65251507A2E4@intel.com>
22/09/2021 08:17, Chen, Zhaoyan:
> 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).
Why a patch failing CI has been merged?
Is it because we get used to have CI failing and don't pay attention?
> 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?
Everybody, every contributors ask why CI is failing for their patch.
So yes, such test should have been disabled as early as you discover the problem please.
The right process is to fill a bugzilla ticket to be referenced in the fix.
next prev parent reply other threads:[~2021-09-22 7:23 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
2021-09-22 7:23 ` Thomas Monjalon [this message]
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=2731761.8huRqIiH2e@thomas \
--to=thomas@monjalon.net \
--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=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).