Re: [dpdk-dev] [dpdk-stable] 18.02.2 patches review and test
On Wed, 2018-06-13 at 08:56 +0200, Marco Varlese wrote: > Luca, > > I ran some smoke tests on 18.02.2 / 17.11.3 and 16.11.7 using > test_pmd and found > no issues with these snapshots. > > Further, I ran some tests via OvS-DPDK and VPP (DPDK accelerated) > using the > aforementioned snapshots and saw no issues. > > Hope this helps. > > > Cheers, > Marco Great, thanks! > On Fri, 2018-06-08 at 10:16 +0100, Luca Boccassi wrote: > > On Mon, 2018-06-04 at 09:58 +0100, Luca Boccassi wrote: > > > Hi all, > > > > > > Here is a list of patches targeted for stable release 18.02.2. > > > Please > > > help review and test. The planned date for the final release is > > > Thursday, > > > the 14th of June. Before that, please shout if anyone has > > > objections > > > with these > > > patches being applied. > > > > > > Also for the companies committed to running regression tests, > > > please run the tests and report any issue before the release > > > date. > > > > > > These patches are located at branch 18.02 of dpdk-stable repo: > > > https://dpdk.org/browse/dpdk-stable/ > > > > > > Thanks. > > > > > > Luca Boccassi > > > > Hi, > > > > The release date for 18.02.2 is being postponed by one day to > > Friday > > the 15th to due to unforeseen delays in some regression tests. > > Apologies for the inconvenience. > > -- Kind regards, Luca Boccassi
Re: [dpdk-dev] [dpdk-stable] 18.02.2 patches review and test
Luca, I ran some smoke tests on 18.02.2 / 17.11.3 and 16.11.7 using test_pmd and found no issues with these snapshots. Further, I ran some tests via OvS-DPDK and VPP (DPDK accelerated) using the aforementioned snapshots and saw no issues. Hope this helps. Cheers, Marco On Fri, 2018-06-08 at 10:16 +0100, Luca Boccassi wrote: > On Mon, 2018-06-04 at 09:58 +0100, Luca Boccassi wrote: > > Hi all, > > > > Here is a list of patches targeted for stable release 18.02.2. > > Please > > help review and test. The planned date for the final release is > > Thursday, > > the 14th of June. Before that, please shout if anyone has > > objections > > with these > > patches being applied. > > > > Also for the companies committed to running regression tests, > > please run the tests and report any issue before the release date. > > > > These patches are located at branch 18.02 of dpdk-stable repo: > > https://dpdk.org/browse/dpdk-stable/ > > > > Thanks. > > > > Luca Boccassi > > Hi, > > The release date for 18.02.2 is being postponed by one day to Friday > the 15th to due to unforeseen delays in some regression tests. > Apologies for the inconvenience. >
Re: [dpdk-dev] [dpdk-stable] 18.02.2 patches review and test
On Thu, 2018-06-07 at 23:10 +, Raslan Darawsheh wrote: > Hi, > We've tested this version and we don't see any new issues. > > Kindest regards, > Raslan Darawsheh Great, thanks for the help! > -Original Message- > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Luca Boccassi > Sent: Monday, June 4, 2018 9:36 PM > To: dpdk stable > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] 18.02.2 patches review and test > > On Mon, 2018-06-04 at 09:58 +0100, Luca Boccassi wrote: > > Hi all, > > > > Here is a list of patches targeted for stable release 18.02.2. > > Please > > help review and test. The planned date for the final release is > > Thursday, the 14th of June. Before that, please shout if anyone > > has > > objections with these patches being applied. > > > > Also for the companies committed to running regression tests, > > please > > run the tests and report any issue before the release date. > > > > These patches are located at branch 18.02 of dpdk-stable repo: > > > > https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2F > > dpd > > k.org%2Fbrowse%2Fdpdk- > > stable%2F&data=02%7C01%7Crasland%40mellanox.com% > > 7Ccba30760511b4833b4cc08d5ca4a057a%7Ca652971c7d2e4d9ba6a4d149256f46 > > 1b% > > 7C0%7C0%7C636637341669500745&sdata=8W%2BszfAznE5zhZQOfIcUINKr4gScR0 > > Z9V > > Wj0m4%2F7n9o%3D&reserved=0 > > > > Thanks. > > > > Luca Boccassi > > > > --- > > The fix for a bad regression in the qat crypto pmd was missed, due to > missing Fixes line in the commit message. It has now been queued on > request of the author: > > Lee Roberts (1): > crypto/qat: assign device to correct NUMA node > > -- > Kind regards, > Luca Boccassi -- Kind regards, Luca Boccassi
