From: Aaron Conole <aconole@redhat.com>
To: "Kundapura, Ganapati" <ganapati.kundapura@intel.com>
Cc: Adam Hassick <ahassick@iol.unh.edu>,
"dpdk-test-reports@iol.unh.edu" <dpdk-test-reports@iol.unh.edu>,
"dpdklab@iol.unh.edu" <dpdklab@iol.unh.edu>,
"test-report@dpdk.org" <test-report@dpdk.org>,
"Jayatheerthan, Jay" <jay.jayatheerthan@intel.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
ci@dpdk.org
Subject: Re: |WARNING| pw113233-113239 [PATCH] [v7, 7/7] doc/eth_tx: update instance get API
Date: Wed, 22 Jun 2022 11:22:36 -0400 [thread overview]
Message-ID: <f7tmte4soxv.fsf@redhat.com> (raw)
In-Reply-To: <MW4PR11MB59111DCF41B1C721EECB0A2387B29@MW4PR11MB5911.namprd11.prod.outlook.com> (Ganapati Kundapura's message of "Wed, 22 Jun 2022 15:00:28 +0000")
Greeting Ganapati,
"Kundapura, Ganapati" <ganapati.kundapura@intel.com> writes:
> Hi Brandon,
Brandon left the lab in April. I've CC'd Adam Hassick, who I think can
probably help.
> This patch is reporting apply warnings
>
> https://lab.dpdk.org/results/dashboard/patchsets/22745/
>
>
>
> Test-Label: iol-testing
>
> Test-Status: WARNING
>
> http://dpdk.org/patch/113233
>
>
>
> _apply patch failure_
Looks like there was a race with updating vs. submitting.
Agree - this should be rerun.
> Submitter: Ganapati Kundapura <ganapati.kundapura at intel.com>
>
> Date: Wednesday, June 22 2022 10:37:56
>
> Applied on: CommitID:9aa95b6fc4d0f166f8364f60c476f52dfcbe1082
>
> Apply patch set 113233-113239 failed:
>
> But it seems that it’s trying to apply on the wrong commit
>
> Applied on dpdk (9aa95b6fc4d0f166f8364f60c476f52dfcbe1082)
>
>
>
> I’m able to apply it on the latest commits of dpdk and dpdk-next-eventdev.
>
Thanks for confirming that at least this can apply and execute on
3227bc7138f5afd7593c0eb4dd6b52710f4193b7 ("crypto/qat: use intel-ipsec-mb for partial hash and AES")
> Most probably the next-eventdev tree is off sync in the lab, can you please check it?
>
> And after the issue is resolved, can you please re-trigger the test for mentioned patch?
I think this should be doable.
> Thanks,
>
> Ganapati
next parent reply other threads:[~2022-06-22 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MW4PR11MB59111DCF41B1C721EECB0A2387B29@MW4PR11MB5911.namprd11.prod.outlook.com>
2022-06-22 15:22 ` Aaron Conole [this message]
2022-06-22 15:25 ` Hassick, Adam C
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=f7tmte4soxv.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=ahassick@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=dpdklab@iol.unh.edu \
--cc=ganapati.kundapura@intel.com \
--cc=jay.jayatheerthan@intel.com \
--cc=jerinj@marvell.com \
--cc=test-report@dpdk.org \
/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).