On Thu, Mar 31, 2022 at 12:00 PM Christian Ehrhardt < christian.ehrha...@canonical.com> wrote:
> > > On Wed, Mar 30, 2022 at 1:04 PM Jiang, YuX <yux.ji...@intel.com> wrote: > >> > -----Original Message----- >> > From: christian.ehrha...@canonical.com < >> christian.ehrha...@canonical.com> >> > Sent: Monday, March 21, 2022 7:55 PM >> > To: sta...@dpdk.org >> > Cc: dev@dpdk.org; Abhishek Marathe <abhishek.mara...@microsoft.com>; >> > Ali Alnubani <alia...@nvidia.com>; Walker, Benjamin >> > <benjamin.wal...@intel.com>; David Christensen >> > <d...@linux.vnet.ibm.com>; hariprasad.govindhara...@intel.com; Hemant >> > Agrawal <hemant.agra...@nxp.com>; Stokes, Ian <ian.sto...@intel.com>; >> > Jerin Jacob <jer...@marvell.com>; Mcnamara, John >> > <john.mcnam...@intel.com>; Ju-Hyoung Lee <juh...@microsoft.com>; >> > Kevin Traynor <ktray...@redhat.com>; Luca Boccassi <bl...@debian.org>; >> > Pei Zhang <pezh...@redhat.com>; Xu, Qian Q <qian.q...@intel.com>; >> > Raslan Darawsheh <rasl...@nvidia.com>; Thomas Monjalon >> > <tho...@monjalon.net>; Peng, Yuan <yuan.p...@intel.com>; Chen, >> > Zhaoyan <zhaoyan.c...@intel.com> >> > Subject: 19.11.12 patches review and test >> > >> > Hi all, >> > >> > Here is a list of patches targeted for stable release 19.11.12. >> > >> > The planned date for the final release is 7th of April. >> > >> > Please help with testing and validation of your use cases and report any >> > issues/results with reply-all to this mail. For the final release the >> fixes and >> > reported validations will be added to the release notes. >> > >> > A release candidate tarball can be found at: >> > >> > https://dpdk.org/browse/dpdk-stable/tag/?id=v19.11.12-rc1 >> > >> > These patches are located at branch 19.11 of dpdk-stable repo: >> > https://dpdk.org/browse/dpdk-stable/ >> > >> > Thanks. >> > >> > Christian Ehrhardt <christian.ehrha...@canonical.com> >> > >> Update the test status for Intel part. DPDK19.11.12-rc1 test rate is 60%, >> totally find four defects as below: >> > > Thank you for all your work! > > >> Bug1:[dpdk-19.11.12] metering_and_policing/ipv4_HASH_table_RFC2698: >> unable to forward packets normally. Intel Dev is investigating. >> Bug2:[LTS DPDK-19.11.12-rc1] cryptodev_qat_asym_autotest is failing. >> Intel Dev is investigating. >> > > Both are very interesting, could you make sure that by next Wednesday (6th > of April) there is feedback on this thread if this is either: > Hi Jiang YuX, by now everything else is in place to tag the 19.11.12 release tomorrow, therefore I wanted to ping for these updates so that we can make the right decision to release or delay. > 1. fixable, with a pointer to a fix > 2. not fixed yet, but also not too bad (or not a regression to the former > state) and thereby does not block 19.11.12 > 3. not fixed yet, but being very severe blocking 19.11.12, but identified > the offending commit that shall be reverted > 4. not fixed yet, but being very severe blocking 19.11.12, and an ETA of a > fix/mitigation > > Based on that outcome we then need to decide if we need to tag -rc2 and > another round of verifications. > > Bug3:https://bugs.dpdk.org/show_bug.cgi?id=978 [dpdk-19.11.12-rc1] >> drivers/net/qede make build failed on Fedora35 with Clang13.0.0. >> > Bad commit from Vanshika Shukla <vanshika.shu...@nxp.com>, no fix yet. >> > > Thanks for identifying this one. > As in the past, we are willing to take build time fixes for newer compiler > stacks, but we are not blocked on releasing 19.11.12 unless platforms > formerly building and using it are affected. > > >> Bug4:https://bugs.dpdk.org/show_bug.cgi?id=977 [dpdk-19.11.12-rc1] >> bnxt_stats meson&&make build Error on Fedora35-64 and Ubuntu2110-64 with >> gcc11.2.1&&gcc11.2.0. >> > Has fix ( >> https://github.com/cpaelzer/dpdk-stable-queue/commit/f17a5eb33a2fec2f33476743f56d1fb2d37ca3b7.patch) >> and verify passed. >> > > Yes thanks, this one is indeed already applied > > >> >> # Basic Intel(R) NIC testing >> * Build: cover the build test combination with latest GCC/Clang/ICC >> version and the popular OS revision such as Ubuntu20.04, Fedora35, RHEL8.4, >> etc. >> - All test done. Two new bugs are found, and one known bug( >> https://bugs.dpdk.org/show_bug.cgi?id=747) >> * PF(i40e, ixgbe): test scenarios including >> RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc. >> - Execution rate is 30%, no new issue is found. >> * VF(i40e, ixgbe): test scenarios including >> VF-RTE_FLOW/TSO/Jumboframe/checksum offload/VLAN/VXLAN, etc. >> - Execution rate is 30%, no new issue is found. >> * PF/VF(ice): test scenarios including Switch features/Package >> Management/Flow Director/Advanced Tx, etc. >> - All test done. No new issue is found. >> * Intel NIC single core/NIC performance: test scenarios including PF/VF >> single core performance test etc. >> - All test done. No big performance drop. >> * IPsec: test scenarios including ipsec/ipsec-gw/ipsec library basic test >> - QAT&SW/FIB library, etc. >> - On going. >> # Basic cryptodev and virtio testing >> * Virtio: both function and performance test are covered. Such as >> PVP/Virtio_loopback/virtio-user loopback/virtio-net VM2VM perf testing, etc. >> - All test done. No new issue is found. >> * Cryptodev: >> * Function test: test scenarios including Cryptodev API >> testing/CompressDev ISA-L/QAT/ZLIB PMD Testing/ etc. >> - On going. >> * Performance test: test scenarios including Thoughput Performance >> /Cryptodev Latency, etc. >> - On going. >> >> BRs >> Yu Jiang >> > > > -- > Christian Ehrhardt > Staff Engineer, Ubuntu Server > Canonical Ltd > -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd
