From: Aaron Conole <aconole@redhat.com>
To: "Power, Ciara" <ciara.power@intel.com>
Cc: "Sivaramakrishnan, VenkatX" <venkatx.sivaramakrishnan@intel.com>,
"Akhil Goyal" <gakhil@marvell.com>, "Ji, Kai" <kai.ji@intel.com>,
"probb@iol.unh.edu" <probb@iol.unh.edu>,
dev@dpdk.org
Subject: Re: reg. https://patches.dpdk.org/project/dpdk/list/?series=31200 - patch result
Date: Tue, 05 Mar 2024 13:37:13 -0500 [thread overview]
Message-ID: <f7ty1awa5k6.fsf@redhat.com> (raw)
In-Reply-To: <SN7PR11MB7639AB757ECB3D039E47B10AE6222@SN7PR11MB7639.namprd11.prod.outlook.com> (Ciara Power's message of "Tue, 5 Mar 2024 10:40:56 +0000")
"Power, Ciara" <ciara.power@intel.com> writes:
> + Patrick
>
>
>
> From: Power, Ciara
> Sent: Tuesday, March 5, 2024 10:05 AM
> To: Sivaramakrishnan, VenkatX <venkatx.sivaramakrishnan@intel.com>; Akhil Goyal <gakhil@marvell.com>
> Cc: Ji, Kai <kai.ji@intel.com>; Aaron Conole <aconole@redhat.com>
> Subject: RE: reg. https://patches.dpdk.org/project/dpdk/list/?series=31200 - patch result
>
>
>
> Hi folks,
>
>
>
> Had a quick look, I can also see this:
>
> crypto/ipsec_mb: IPSec_MB version >= 1.4.0 is required, found version 1.2.0
This version of ipsec_mb is less than 1 year old. Did this pass any
other CI testing? I would be surprised if it did - I'm not sure any
downstream environments that would be using it already.
> I guess the installed PMD .so file isn’t created because they are not compiled in, due to the minimum version on
> environment not meeting the new requirements.
I don't see any such new requirements anywhere on the crypto tree. The
only change I know about was for QAT to try and default to IPSec_MB 1.4,
but it is supposed to fall back to OpenSSL if that is unavailable. Did
this change?
> CC’ing Aaron, who might know about upgrading that environment to ipsec-mb v1.4.
>
>
>
> Thanks,
>
> Ciara
>
>
>
> From: Sivaramakrishnan, VenkatX <venkatx.sivaramakrishnan@intel.com>
> Sent: Monday, March 4, 2024 10:45 AM
> To: Akhil Goyal <gakhil@marvell.com>
> Cc: Ji, Kai <kai.ji@intel.com>; Power, Ciara <ciara.power@intel.com>
> Subject: reg. https://patches.dpdk.org/project/dpdk/list/?series=31200 - patch result
>
>
>
> Hi Akhil,
>
>
>
> I would like to provide details of the failures
>
>
>
>
>
> *
>
>
>
>
>
> Failures details:
>
> ============
>
> "Build and test" failed for "librte_crypto_ipsec_mb.so".
>
> doc: remove outdated version details · ovsrobot/dpdk@f40ab34 (github.com)
>
> Error: cannot find librte_crypto_ipsec_mb.so.24.0 in install
>
>
>
> Looks like, “ipsec mb” was not installed on the server.
>
>
>
> However, the patch changes are related to the Doc update. Hope that this will not impact patch merging
>
>
>
> Thank you.
>
>
>
> Best Regards,
>
> Venkat.
next parent reply other threads:[~2024-03-05 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CH3PR11MB85898465A351CD7EEFDB707682232@CH3PR11MB8589.namprd11.prod.outlook.com>
[not found] ` <SN7PR11MB7639AB757ECB3D039E47B10AE6222@SN7PR11MB7639.namprd11.prod.outlook.com>
2024-03-05 18:37 ` Aaron Conole [this message]
2024-03-06 12:20 ` Power, Ciara
2024-03-06 14:57 ` Aaron Conole
2024-03-06 16:57 ` Power, Ciara
2024-03-08 19:39 ` Aaron Conole
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=f7ty1awa5k6.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=kai.ji@intel.com \
--cc=probb@iol.unh.edu \
--cc=venkatx.sivaramakrishnan@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).