From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>,
Qi Zhang <qi.z.zhang@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Cc: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
Lincoln Lavoie <lylavoie@iol.unh.edu>,
"Tu, Lijuan" <lijuan.tu@intel.com>, sys_stv <sys_stv@intel.com>,
"ci@dpdk.org" <ci@dpdk.org>, Aaron Conole <aconole@redhat.com>
Subject: Re: [dpdk-ci] Failing pf_smoke test
Date: Wed, 22 Sep 2021 11:52:59 +0200 [thread overview]
Message-ID: <CAJFAV8z0mCdHGDvKv2QKNDfgVj7k+1=RLCPjGj51nFO__JJKew@mail.gmail.com> (raw)
In-Reply-To: <2731761.8huRqIiH2e@thomas>
On Wed, Sep 22, 2021 at 9:23 AM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 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?
The CI did report this failure on the original series.
http://mails.dpdk.org/archives/test-report/2021-August/210297.html
This series should not have been merged but it was on 08/29:
https://inbox.dpdk.org/dev/0935a75ef4334a4c9af65ecb6adac33f@intel.com/
I am not sure when it got into next-net.
A revert was proposed before next-net pull in main on 09/07:
http://patches.dpdk.org/project/dpdk/patch/20210907064537.74596-1-wenjun1.wu@intel.com/
Note, at this point, I had not noticed the original patch had
triggered a regression.
This revert was then deemed not appropriate and in the end the
original series hit the main branch.
--
David Marchand
next prev parent reply other threads:[~2021-09-22 9:53 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
2021-09-22 9:12 ` Chen, Zhaoyan
2021-09-22 9:52 ` David Marchand [this message]
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='CAJFAV8z0mCdHGDvKv2QKNDfgVj7k+1=RLCPjGj51nFO__JJKew@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=lijuan.tu@intel.com \
--cc=lylavoie@iol.unh.edu \
--cc=qi.z.zhang@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).