All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yu, PingX" <pingx.yu@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	"announce@dpdk.org" <announce@dpdk.org>
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"O'Hare, Cathal" <cathal.ohare@intel.com>,
	"Devlin, Michelle" <michelle.devlin@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 20.11-rc3
Date: Mon, 9 Nov 2020 09:23:59 +0000	[thread overview]
Message-ID: <BY5PR11MB3973CC7709B54B0FF377D2C085EA0@BY5PR11MB3973.namprd11.prod.outlook.com> (raw)
In-Reply-To: <BY5PR11MB3973E5A520C5E4099C54A33285EA0@BY5PR11MB3973.namprd11.prod.outlook.com>

+ Dev@dpdk.org

Regards,
Yu Ping

> -----Original Message-----
> From: Yu, PingX
> Sent: Monday, November 9, 2020 5:06 PM
> To: Thomas Monjalon <thomas@monjalon.net>; announce@dpdk.org
> Cc: Yigit, Ferruh <ferruh.yigit@intel.com>; O'Hare, Cathal
> <cathal.ohare@intel.com>; Devlin, Michelle <michelle.devlin@intel.com>
> Subject: RE: [dpdk-announce] release candidate 20.11-rc3
> 
> All,
> Update the test status for Intel part.  Till now 70% is executed, 2 core dump
> issues are found.
> - CVL 25G iavf core dumped when starting l3fwd: patch is provided and verify
> passed.  http://patches.dpdk.org/patch/83829/
> - Core dumped after running "port reset all" on NIC CVL. Dev is debugging on
> it.
> 
> # Basic Intel(R) NIC testing
> *	PF/VF(i40e,ixgbe and igb): 60% is tested. 2 issues are found.
>     1) can't start pdump: https://bugs.dpdk.org/show_bug.cgi?id=571
>     2) rss to rte flow: created rule failed: Invalid argument:
> https://bugs.dpdk.org/show_bug.cgi?id=573
> *	PF/VF(ICE): 40% is tested. 2 core dump issues are found till now. See
> above.
> *	Build or compile: 100%. 2 known CFLAG compile issue. No new issue
> till now.
> *	Intel NIC single core/NIC performance:  80% is tested. the issues are
> the same as function test.
> *	Power and IPsec: Not start yet.
> *	Other 20.11 new features: 30% is tested. No critical issue till now.
> 
> # Basic cryptodev and virtio testing
> *	Virtio: 60% is tested. Except known issue, no new issue till now.
> *	Cryptodev: function test is 100%. No new issue. Performance is
> testing.
> 
> Regards,
> Yu Ping
> 
> > -----Original Message-----
> > From: announce <announce-bounces@dpdk.org> On Behalf Of Thomas
> > Monjalon
> > Sent: Friday, November 6, 2020 3:32 AM
> > To: announce@dpdk.org
> > Subject: [dpdk-announce] release candidate 20.11-rc3
> >
> > A new DPDK release candidate is ready for testing:
> > 	https://git.dpdk.org/dpdk/tag/?id=v20.11-rc3
> >
> > There are only 9 new patches since yesterday -rc2, including a revert
> > which should unblock a lot of testing cases with testpmd.
> >
> > Release notes:
> > 	http://doc.dpdk.org/guides/rel_notes/release_20_11.html
> >
> > As a consequence of this hot fix release, -rc numbering is shifted.
> > The -rc4 should include only some bug fixes, cleanups, doc and tooling.
> > We have until the end of next week to complete this milestone.
> > Then at least one more week (allowing -rc5) should be needed before
> > the release.
> >
> > Please test, report and fix issues on bugs.dpdk.org.
> > As a community, we must close as many bugs as possible for -rc4.
> >
> > We are getting even much closer to a well deserved rest.
> > Thank you everyone
> >


       reply	other threads:[~2020-11-09  9:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BY5PR11MB3973E5A520C5E4099C54A33285EA0@BY5PR11MB3973.namprd11.prod.outlook.com>
2020-11-09  9:23 ` Yu, PingX [this message]
2020-11-11  9:22   ` [dpdk-dev] [dpdk-announce] release candidate 20.11-rc3 Yu, PingX
2020-11-05 19:32 Thomas Monjalon

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=BY5PR11MB3973CC7709B54B0FF377D2C085EA0@BY5PR11MB3973.namprd11.prod.outlook.com \
    --to=pingx.yu@intel.com \
    --cc=announce@dpdk.org \
    --cc=cathal.ohare@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=michelle.devlin@intel.com \
    --cc=thomas@monjalon.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.