[dpdk-ci] dpdk-next-crypto/master is failing tests

[dpdk-ci] dpdk-next-crypto/master is failing tests

[Owen Hilyard]

[-- Attachment #1: Type: text/plain, Size: 564 bytes --]

The Intel 10G and Intel 40G systems at the community lab had test jobs
begin to crash a few hours ago. This was the result of DTS crashing
severely enough that the job was unable to continue. A brief investigation
makes it seem like the "-a" flag for testpmd has been removed, which is
causing the timeout. Logs and the tarball which caused the issue are
attached.
 dpdk.tar.gz
<https://drive.google.com/file/d/1wIMnKdHJ6RMa-Xf76W1riDrdDjRQK5SD/view?usp=drive_web>
 output.zip
<https://drive.google.com/file/d/10W6d4bcyr5oEpG8KWRszw0rTIuKe7jIC/view?usp=drive_web>

[-- Attachment #2: Type: text/html, Size: 2169 bytes --]

Re: [dpdk-ci] dpdk-next-crypto/master is failing tests

[Thomas Monjalon]

05/05/2021 23:31, Owen Hilyard:
> The Intel 10G and Intel 40G systems at the community lab had test jobs
> begin to crash a few hours ago. This was the result of DTS crashing
> severely enough that the job was unable to continue. A brief investigation
> makes it seem like the "-a" flag for testpmd has been removed, which is
> causing the timeout. Logs and the tarball which caused the issue are
> attached.
>  dpdk.tar.gz
> <https://drive.google.com/file/d/1wIMnKdHJ6RMa-Xf76W1riDrdDjRQK5SD/view?usp=drive_web>
>  output.zip
> <https://drive.google.com/file/d/10W6d4bcyr5oEpG8KWRszw0rTIuKe7jIC/view?usp=drive_web>

Looking at the version in the archive, it is dpdk-20.11-rc0.
Something is wrong in the lab.

Re: [dpdk-ci] dpdk-next-crypto/master is failing tests

[David Marchand]

On Wed, May 5, 2021 at 11:52 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 05/05/2021 23:31, Owen Hilyard:
> > The Intel 10G and Intel 40G systems at the community lab had test jobs
> > begin to crash a few hours ago. This was the result of DTS crashing
> > severely enough that the job was unable to continue. A brief investigation
> > makes it seem like the "-a" flag for testpmd has been removed, which is
> > causing the timeout. Logs and the tarball which caused the issue are
> > attached.
> >  dpdk.tar.gz
> > <https://drive.google.com/file/d/1wIMnKdHJ6RMa-Xf76W1riDrdDjRQK5SD/view?usp=drive_web>
> >  output.zip
> > <https://drive.google.com/file/d/10W6d4bcyr5oEpG8KWRszw0rTIuKe7jIC/view?usp=drive_web>
>
> Looking at the version in the archive, it is dpdk-20.11-rc0.


- For the dpdk-next-crypto branch (that I suppose is the reference for
testing crypto patches), the HEAD is at "dpdk-next-crypto/master".
IIRC, we moved away for the "master" name for branches in August 2020.
$ git ll |head -2
f694bded31 - (HEAD -> temp) test/crypto: copy offset data to oop dst
buffer (31 hours ago) <Kai Ji>
8b6b2bf6b5 - (dpdk-next-crypto/master, dpdk-next-crypto) test/service:
fix race condition on stopping lcore (8 months ago) <Harry van Haaren>


- TLDR: the dpdk-next-virtio branch needs fixing too.

Bonus:
* the dpdk-next-pipeline and dpdk-next-qos remotes are unused and can
be dropped,
* the master, dpdk-next-pipeline, dpdk-next-qos branches are unused
and can be dropped,
* references to /master branches can be dropped,


Details:

$ for tree in $(git remote -v |awk '/fetch/ {print $2}'); do grep -q
"^T: $tree" MAINTAINERS || echo $tree; done
git://dpdk.org/next/dpdk-next-pipeline
git://dpdk.org/next/dpdk-next-qos

The dpdk-next-pipeline and dpdk-next-qos remotes can be removed, those
trees are not used anymore.


$ for branch in $(git branch |grep -v temp); do git ll
refs/heads/$branch |head -1; done
caec80f92a - (dpdk/main, dpdk-next-crypto/for-main, main, dpdk)
common/mlx5: add UMR and RDMA write WQE definitions (34 hours ago)
<Suanming Mou>
8b6b2bf6b5 - (dpdk-next-crypto/master, dpdk-next-crypto) test/service:
fix race condition on stopping lcore (8 months ago) <Harry van Haaren>
             ^^
             This is the issue that triggered this mail.
13116d6e86 - (dpdk-next-eventdev/for-main, dpdk-next-eventdev)
event/cnxk: add devargs to control timer adapters (2 days ago)
<Shijith Thotton>
e50ca76c69 - (dpdk-next-net-brcm/pre-submit, dpdk-next-net-brcm/main,
dpdk-next-net-brcm/for-next-net, dpdk-next-net-brcm, dpdk-next-net)
net/mlx5: fix TCP flags size for modify actions (3 days ago) <Wisam
Jaddo>
e50ca76c69 - (dpdk-next-net-brcm/pre-submit, dpdk-next-net-brcm/main,
dpdk-next-net-brcm/for-next-net, dpdk-next-net-brcm, dpdk-next-net)
net/mlx5: fix TCP flags size for modify actions (3 days ago) <Wisam
Jaddo>
f21ea9c424 - (dpdk-next-net-intel/main,
dpdk-next-net-intel/for-next-net, dpdk-next-net-intel) net/iavf: fix
VLAN tag extraction handling in AVX512 path (6 days ago) <Leyi Rong>
fd09e24352 - (dpdk-next-net-mlx/main, dpdk-next-net-mlx/for-next-net,
dpdk-next-net-mlx) net/mlx5: fix tunnel offload private items location
(2 days ago) <Gregory Etelson>
156527cfb9 - (dpdk-next-net-mrvl/for-main, dpdk-next-net-mrvl)
net/octeontx2: support flow action port id (6 weeks ago) <Smadar Fuks>
830410b265 - (tag: v18.05-rc6, dpdk-next-pipeline) version: 18.05-rc6
(2 years, 11 months ago) <Thomas Monjalon>
             ^^
             This branch can be dropped, since associated patches are
supposed to be tested against the main dpdk repo/branch.
89f6a4be21 - (dpdk-next-virtio/master, dpdk-next-virtio) vdpa/mlx5:
fix virtq unset (9 months ago) <Matan Azrad>
             ^^
             dpdk-next-virtio needs fixing. Like dpdk-next-crypto,
dpdk-next-virtio references the old master branch.
caec80f92a - (dpdk/main, dpdk-next-crypto/for-main, main, dpdk)
common/mlx5: add UMR and RDMA write WQE definitions (34 hours ago)
<Suanming Mou>
d218a4d060 - (master) doc: add meter API change to release notes (3
years, 1 month ago) <Jasvinder Singh>
             ^^
             This branch can be dropped.


$ git branch -lr |grep /master
  dpdk-next-crypto/master
  dpdk-next-eventdev/master
  dpdk-next-net-brcm/master
  dpdk-next-net-intel/master
  dpdk-next-net-mlx/master
  dpdk-next-net-mrvl/master
  dpdk-next-net/master
  dpdk-next-pipeline/master
  dpdk-next-virtio/master
  dpdk/HEAD -> dpdk/master
  dpdk/master

Those remote tracking branches can be dropped.


-- 
David Marchand

Re: [dpdk-ci] dpdk-next-crypto/master is failing tests

[Brandon Lo]

Hi all,

dpdk-next-qos and dpdk-next-pipeline remotes have been removed.
dpdk-next-virtio and dpdk-next-crypto remotes have been switched to
track main and for-main branches respectively.

Thanks,
Brandon

On Thu, May 6, 2021 at 3:32 AM David Marchand <david.marchand@redhat.com> wrote:
>
> On Wed, May 5, 2021 at 11:52 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> >
> > 05/05/2021 23:31, Owen Hilyard:
> > > The Intel 10G and Intel 40G systems at the community lab had test jobs
> > > begin to crash a few hours ago. This was the result of DTS crashing
> > > severely enough that the job was unable to continue. A brief investigation
> > > makes it seem like the "-a" flag for testpmd has been removed, which is
> > > causing the timeout. Logs and the tarball which caused the issue are
> > > attached.
> > >  dpdk.tar.gz
> > > <https://drive.google.com/file/d/1wIMnKdHJ6RMa-Xf76W1riDrdDjRQK5SD/view?usp=drive_web>
> > >  output.zip
> > > <https://drive.google.com/file/d/10W6d4bcyr5oEpG8KWRszw0rTIuKe7jIC/view?usp=drive_web>
> >
> > Looking at the version in the archive, it is dpdk-20.11-rc0.
>
>
> - For the dpdk-next-crypto branch (that I suppose is the reference for
> testing crypto patches), the HEAD is at "dpdk-next-crypto/master".
> IIRC, we moved away for the "master" name for branches in August 2020.
> $ git ll |head -2
> f694bded31 - (HEAD -> temp) test/crypto: copy offset data to oop dst
> buffer (31 hours ago) <Kai Ji>
> 8b6b2bf6b5 - (dpdk-next-crypto/master, dpdk-next-crypto) test/service:
> fix race condition on stopping lcore (8 months ago) <Harry van Haaren>
>
>
> - TLDR: the dpdk-next-virtio branch needs fixing too.
>
> Bonus:
> * the dpdk-next-pipeline and dpdk-next-qos remotes are unused and can
> be dropped,
> * the master, dpdk-next-pipeline, dpdk-next-qos branches are unused
> and can be dropped,
> * references to /master branches can be dropped,
>
>
> Details:
>
> $ for tree in $(git remote -v |awk '/fetch/ {print $2}'); do grep -q
> "^T: $tree" MAINTAINERS || echo $tree; done
> git://dpdk.org/next/dpdk-next-pipeline
> git://dpdk.org/next/dpdk-next-qos
>
> The dpdk-next-pipeline and dpdk-next-qos remotes can be removed, those
> trees are not used anymore.
>
>
> $ for branch in $(git branch |grep -v temp); do git ll
> refs/heads/$branch |head -1; done
> caec80f92a - (dpdk/main, dpdk-next-crypto/for-main, main, dpdk)
> common/mlx5: add UMR and RDMA write WQE definitions (34 hours ago)
> <Suanming Mou>
> 8b6b2bf6b5 - (dpdk-next-crypto/master, dpdk-next-crypto) test/service:
> fix race condition on stopping lcore (8 months ago) <Harry van Haaren>
>              ^^
>              This is the issue that triggered this mail.
> 13116d6e86 - (dpdk-next-eventdev/for-main, dpdk-next-eventdev)
> event/cnxk: add devargs to control timer adapters (2 days ago)
> <Shijith Thotton>
> e50ca76c69 - (dpdk-next-net-brcm/pre-submit, dpdk-next-net-brcm/main,
> dpdk-next-net-brcm/for-next-net, dpdk-next-net-brcm, dpdk-next-net)
> net/mlx5: fix TCP flags size for modify actions (3 days ago) <Wisam
> Jaddo>
> e50ca76c69 - (dpdk-next-net-brcm/pre-submit, dpdk-next-net-brcm/main,
> dpdk-next-net-brcm/for-next-net, dpdk-next-net-brcm, dpdk-next-net)
> net/mlx5: fix TCP flags size for modify actions (3 days ago) <Wisam
> Jaddo>
> f21ea9c424 - (dpdk-next-net-intel/main,
> dpdk-next-net-intel/for-next-net, dpdk-next-net-intel) net/iavf: fix
> VLAN tag extraction handling in AVX512 path (6 days ago) <Leyi Rong>
> fd09e24352 - (dpdk-next-net-mlx/main, dpdk-next-net-mlx/for-next-net,
> dpdk-next-net-mlx) net/mlx5: fix tunnel offload private items location
> (2 days ago) <Gregory Etelson>
> 156527cfb9 - (dpdk-next-net-mrvl/for-main, dpdk-next-net-mrvl)
> net/octeontx2: support flow action port id (6 weeks ago) <Smadar Fuks>
> 830410b265 - (tag: v18.05-rc6, dpdk-next-pipeline) version: 18.05-rc6
> (2 years, 11 months ago) <Thomas Monjalon>
>              ^^
>              This branch can be dropped, since associated patches are
> supposed to be tested against the main dpdk repo/branch.
> 89f6a4be21 - (dpdk-next-virtio/master, dpdk-next-virtio) vdpa/mlx5:
> fix virtq unset (9 months ago) <Matan Azrad>
>              ^^
>              dpdk-next-virtio needs fixing. Like dpdk-next-crypto,
> dpdk-next-virtio references the old master branch.
> caec80f92a - (dpdk/main, dpdk-next-crypto/for-main, main, dpdk)
> common/mlx5: add UMR and RDMA write WQE definitions (34 hours ago)
> <Suanming Mou>
> d218a4d060 - (master) doc: add meter API change to release notes (3
> years, 1 month ago) <Jasvinder Singh>
>              ^^
>              This branch can be dropped.
>
>
> $ git branch -lr |grep /master
>   dpdk-next-crypto/master
>   dpdk-next-eventdev/master
>   dpdk-next-net-brcm/master
>   dpdk-next-net-intel/master
>   dpdk-next-net-mlx/master
>   dpdk-next-net-mrvl/master
>   dpdk-next-net/master
>   dpdk-next-pipeline/master
>   dpdk-next-virtio/master
>   dpdk/HEAD -> dpdk/master
>   dpdk/master
>
> Those remote tracking branches can be dropped.
>
>
> --
> David Marchand
>


-- 

Brandon Lo

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

blo@iol.unh.edu

www.iol.unh.edu

Re: [dpdk-ci] dpdk-next-crypto/master is failing tests

[David Marchand]

On Thu, May 6, 2021 at 6:15 PM Brandon Lo <blo@iol.unh.edu> wrote:
>
> Hi all,
>
> dpdk-next-qos and dpdk-next-pipeline remotes have been removed.
> dpdk-next-virtio and dpdk-next-crypto remotes have been switched to
> track main and for-main branches respectively.

Thank you Brandon.

Just an additional question.

In the lab dashboard, I can find status/test reports for the most
repositories, like main, next-net, next-net-intel.
https://lab.dpdk.org/results/dashboard/tarballs/

But I can't find next-virtio or next-crypto.
Are they tested / supposed to land in this part of the dashboard?


-- 
David Marchand

Re: [dpdk-ci] dpdk-next-crypto/master is failing tests

[Brandon Lo]

Hi David,

Sorry for the late reply.
This may be due to the configuration with Jenkins on our side.
If I do not see that next-virtio and next-crypto are in Jenkins, I can
definitely add it in.

Thanks,
Brandon

On Tue, May 11, 2021 at 9:54 AM David Marchand
<david.marchand@redhat.com> wrote:
>
> On Thu, May 6, 2021 at 6:15 PM Brandon Lo <blo@iol.unh.edu> wrote:
> >
> > Hi all,
> >
> > dpdk-next-qos and dpdk-next-pipeline remotes have been removed.
> > dpdk-next-virtio and dpdk-next-crypto remotes have been switched to
> > track main and for-main branches respectively.
>
> Thank you Brandon.
>
> Just an additional question.
>
> In the lab dashboard, I can find status/test reports for the most
> repositories, like main, next-net, next-net-intel.
> https://lab.dpdk.org/results/dashboard/tarballs/
>
> But I can't find next-virtio or next-crypto.
> Are they tested / supposed to land in this part of the dashboard?
>
>
> --
> David Marchand
>


-- 

Brandon Lo

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

blo@iol.unh.edu

www.iol.unh.edu