From: Thomas Monjalon <email@example.com>
To: Qi Zhang <firstname.lastname@example.org>,
"Yigit, Ferruh" <email@example.com>,
David Marchand <firstname.lastname@example.org>,
"Chen, Zhaoyan" <email@example.com>
Cc: Lincoln Lavoie <firstname.lastname@example.org>,
"Tu, Lijuan" <email@example.com>, sys_stv <firstname.lastname@example.org>,
"email@example.com" <firstname.lastname@example.org>, Aaron Conole <email@example.com>
Subject: Re: [dpdk-ci] Failing pf_smoke test
Date: Wed, 22 Sep 2021 12:02:33 +0200 [thread overview]
Message-ID: <3438602.BVhvIeFHnb@thomas> (raw)
22/09/2021 11:52, David Marchand:
> On Wed, Sep 22, 2021 at 9:23 AM Thomas Monjalon <firstname.lastname@example.org> 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.
> This series should not have been merged but it was on 08/29:
> I am not sure when it got into next-net.
> A revert was proposed before next-net pull in main on 09/07:
> 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.
Thanks for the history.
We must improve to avoid such failure in future.
next prev parent reply other threads:[~2021-09-22 10:02 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
2021-09-22 10:02 ` Thomas Monjalon [this message]
2021-09-30 7:58 ` David Marchand
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 \
* 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).