From: David Marchand <david.marchand@redhat.com>
To: "Jiang, YuX" <yux.jiang@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
"dev (dev@dpdk.org)" <dev@dpdk.org>,
"Devlin, Michelle" <michelle.devlin@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 21.11-rc2
Date: Thu, 11 Nov 2021 09:57:33 +0100 [thread overview]
Message-ID: <CAJFAV8zKcL0ONCYHv3wQ-JWK9576aSHuJbSR3AS6XF7pNq4EFg@mail.gmail.com> (raw)
In-Reply-To: <SJ0PR11MB5150C3005E47BE2B0A334CBBFE949@SJ0PR11MB5150.namprd11.prod.outlook.com>
On Thu, Nov 11, 2021 at 9:26 AM Jiang, YuX <yux.jiang@intel.com> wrote:
> Update the test status for Intel part. Till now dpdk21.11-rc2 test execution rate is 85%. No critical issue is found.
> But has some about missing '_mm512_set_epi8' support build issues. Intel has already sent a fix:
> Patch Link: https://patches.dpdk.org/project/dpdk/patch/20211109172456.147140-1-vladimir.medvedkin@intel.com/
>
> # Basic Intel(R) NIC testing
> * Build or compile:
> *Build: cover the build test combination with latest GCC/Clang/ICC version and the popular OS revision such as Ubuntu20.04, Fedora34, RHEL8.4, etc.
> - All test done.
> - One bug about lib/librte_power.a.p build failed on OS Fedora35 with clang 13.0.0 is found.
> - Has fix patch for litrte_power, verify patch but find new failure, report bugzilla for new failure about fslmc.
Thanks, I added more details in https://bugs.dpdk.org/show_bug.cgi?id=881
--
David Marchand
next prev parent reply other threads:[~2021-11-11 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 0:45 Thomas Monjalon
2021-11-11 8:25 ` Jiang, YuX
2021-11-11 8:57 ` David Marchand [this message]
2021-11-16 7:13 ` Jiang, YuX
2021-11-15 4:34 ` Pei Zhang
2021-11-15 5:00 ` [dpdk-dev] " Kalesh Anakkur Purayil
2021-11-17 19:56 ` Thinh Tran
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=CAJFAV8zKcL0ONCYHv3wQ-JWK9576aSHuJbSR3AS6XF7pNq4EFg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=michelle.devlin@intel.com \
--cc=thomas@monjalon.net \
--cc=yux.jiang@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).