From: David Marchand <david.marchand@redhat.com>
To: "Naga Harish K, S V" <s.v.naga.harish.k@intel.com>,
dpdklab <dpdklab@iol.unh.edu>
Cc: "aconole@redhat.com" <aconole@redhat.com>,
"ahassick@iol.unh.edu" <ahassick@iol.unh.edu>,
"Jayatheerthan, Jay" <jay.jayatheerthan@intel.com>,
Jerin Jacob <jerinjacobk@gmail.com>,
"dev@dpdk.org" <dev@dpdk.org>,
ci@dpdk.org
Subject: Re: facing _apply patch failure_ warning
Date: Tue, 27 Sep 2022 11:19:19 +0200 [thread overview]
Message-ID: <CAJFAV8xoPqE6uy0=cZUcEdPEs-8wqMmXnYZgbCOJq=xO5LEJfQ@mail.gmail.com> (raw)
In-Reply-To: <DM6PR11MB3868F91634EE7F8C891F8951A1559@DM6PR11MB3868.namprd11.prod.outlook.com>
Hello,
Please, don't top post, I reordered your reply to keep the context in
a logical order.
On Tue, Sep 27, 2022 at 11:06 AM Naga Harish K, S V
<s.v.naga.harish.k@intel.com> wrote:
> > From: David Marchand <david.marchand@redhat.com>
> > On Mon, Sep 26, 2022 at 9:54 AM Naga Harish K, S V
> > > I am facing _apply patch failure_ warning for one of my patchsets as
> > below.
> > >
> > > https://lab.dpdk.org/results/dashboard/patchsets/23622/
> > >
> > > http://mails.dpdk.org/archives/test-report/2022-September/309233.html
> > >
> > > Looks like the patch is being applied for dpdk branch, but the patchset is for
> > “dpdk-next-eventdev” branch.
> >
> > Testing locally, the script seems to correctly identify the branch:
> > $ ./tools/pw_maintainers_cli.py --pw-server
> > https://patchwork.dpdk.org/api/1.2 --pw-project dpdk --pw-token XXX list-
> > trees --type series 24817 dpdk-next-eventdev
> >
> > Not sure what went wrong.
> >
> > >
> > > Can you help in applying the patch to correct branch (dpdk-next-
> > eventdev)?
> >
> > I manually triggered a test of this patch against this branch.
>
> Hi David,
> Thanks for triggering test.
> The "_apply patch failure_" warning still shows for the patch. Is this fine?
I guess the UNH CI does not send a report clearing a previous error.
This might be something to fix (ping @UNH, low priority in any case).
In any case, this warning is not a reason to block your patch.
--
David Marchand
parent reply other threads:[~2022-09-27 9:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <DM6PR11MB3868F91634EE7F8C891F8951A1559@DM6PR11MB3868.namprd11.prod.outlook.com>]
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='CAJFAV8xoPqE6uy0=cZUcEdPEs-8wqMmXnYZgbCOJq=xO5LEJfQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=ahassick@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=dpdklab@iol.unh.edu \
--cc=jay.jayatheerthan@intel.com \
--cc=jerinjacobk@gmail.com \
--cc=s.v.naga.harish.k@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).