automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Dengdui Huang <huangdengdui@huawei.com>
Subject: |FAILURE| pw138202-138203 [PATCH] [3/3] app/testpmd: support setting
Date: Tue, 12 Mar 2024 03:44:16 -0700 (PDT)	[thread overview]
Message-ID: <65f03200.050a0220.3afae.8d89SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240312075238.3319480-4-huangdengdui@huawei.com>

Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/138203

_Testing issues_

Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Tuesday, March 12 2024 07:52:38 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e3faaed01e14ffdfe8f4190030540ed874184b55

138202-138203 --> testing fail

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | FAIL           |
+---------------------+----------------+
| CentOS Stream 8     | FAIL           |
+---------------------+----------------+
| CentOS Stream 9     | FAIL           |
+---------------------+----------------+
| Debian Bullseye     | FAIL           |
+---------------------+----------------+
| Debian 12 (arm)     | FAIL           |
+---------------------+----------------+
| Fedora 37           | FAIL           |
+---------------------+----------------+
| Fedora 38           | FAIL           |
+---------------------+----------------+
| openSUSE Leap 15    | FAIL           |
+---------------------+----------------+
| Ubuntu 20.04        | FAIL           |
+---------------------+----------------+
| RHEL8               | FAIL           |
+---------------------+----------------+

==== 20 line log output for RHEL8 (dpdk_unit_test): ====
'./librte_vdpa_ifc.so.24.1' -> 'dpdk/pmds-24.1/librte_vdpa_ifc.so.24.1'
'./librte_vdpa_mlx5.so' -> 'dpdk/pmds-24.1/librte_vdpa_mlx5.so'
'./librte_vdpa_mlx5.so.24' -> 'dpdk/pmds-24.1/librte_vdpa_mlx5.so.24'
'./librte_vdpa_mlx5.so.24.1' -> 'dpdk/pmds-24.1/librte_vdpa_mlx5.so.24.1'
'./librte_vdpa_nfp.so' -> 'dpdk/pmds-24.1/librte_vdpa_nfp.so'
'./librte_vdpa_nfp.so.24' -> 'dpdk/pmds-24.1/librte_vdpa_nfp.so.24'
'./librte_vdpa_nfp.so.24.1' -> 'dpdk/pmds-24.1/librte_vdpa_nfp.so.24.1'
'./librte_vdpa_sfc.so' -> 'dpdk/pmds-24.1/librte_vdpa_sfc.so'
'./librte_vdpa_sfc.so.24' -> 'dpdk/pmds-24.1/librte_vdpa_sfc.so.24'
'./librte_vdpa_sfc.so.24.1' -> 'dpdk/pmds-24.1/librte_vdpa_sfc.so.24.1'

Installing /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/usertools/dpdk-devbind.py to /usr/local/bin
Installing /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/usertools/dpdk-pmdinfo.py to /usr/local/bin
Installing /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/usertools/dpdk-telemetry.py to /usr/local/bin
Installing /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/usertools/dpdk-hugepages.py to /usr/local/bin
Installing /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/usertools/dpdk-rss-flows.py to /usr/local/bin
Installing /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/rte_build_config.h to /usr/local/include
Installing /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/meson-private/libdpdk-libs.pc to /usr/local/lib64/pkgconfig
Installing /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/meson-private/libdpdk.pc to /usr/local/lib64/pkgconfig
Running custom install script '/bin/sh /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/config/../buildtools/symlink-drivers-solibs.sh lib64 dpdk/pmds-24.1'
==== End log output ====

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 11

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29510/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-03-12 10:44 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240312075238.3319480-4-huangdengdui@huawei.com>
2024-03-12  7:32 ` |SUCCESS| pw138202-138203 [PATCH 3/3] app/testpmd: support setting lanes qemudev
2024-03-12  7:36 ` |FAILURE| " qemudev
2024-03-12  7:53 ` |SUCCESS| pw138203 " checkpatch
2024-03-12  8:42 ` |FAILURE| " 0-day Robot
2024-03-12  9:50 ` |SUCCESS| pw138202-138203 [PATCH] [3/3] app/testpmd: support setting dpdklab
2024-03-12  9:59 ` dpdklab
2024-03-12 10:12 ` dpdklab
2024-03-12 10:12 ` dpdklab
2024-03-12 10:13 ` dpdklab
2024-03-12 10:13 ` dpdklab
2024-03-12 10:14 ` dpdklab
2024-03-12 10:21 ` dpdklab
2024-03-12 10:22 ` dpdklab
2024-03-12 10:22 ` dpdklab
2024-03-12 10:23 ` dpdklab
2024-03-12 10:23 ` |WARNING| " dpdklab
2024-03-12 10:23 ` |SUCCESS| " dpdklab
2024-03-12 10:23 ` |FAILURE| " dpdklab
2024-03-12 10:23 ` |WARNING| " dpdklab
2024-03-12 10:23 ` dpdklab
2024-03-12 10:24 ` |SUCCESS| " dpdklab
2024-03-12 10:24 ` dpdklab
2024-03-12 10:24 ` dpdklab
2024-03-12 10:24 ` dpdklab
2024-03-12 10:25 ` dpdklab
2024-03-12 10:25 ` dpdklab
2024-03-12 10:25 ` dpdklab
2024-03-12 10:25 ` dpdklab
2024-03-12 10:26 ` dpdklab
2024-03-12 10:29 ` |WARNING| " dpdklab
2024-03-12 10:30 ` |SUCCESS| " dpdklab
2024-03-12 10:31 ` |WARNING| " dpdklab
2024-03-12 10:31 ` dpdklab
2024-03-12 10:32 ` |SUCCESS| " dpdklab
2024-03-12 10:32 ` dpdklab
2024-03-12 10:33 ` dpdklab
2024-03-12 10:33 ` |WARNING| " dpdklab
2024-03-12 10:34 ` dpdklab
2024-03-12 10:34 ` |SUCCESS| " dpdklab
2024-03-12 10:34 ` |FAILURE| " dpdklab
2024-03-12 10:35 ` |SUCCESS| " dpdklab
2024-03-12 10:35 ` |WARNING| " dpdklab
2024-03-12 10:35 ` |SUCCESS| " dpdklab
2024-03-12 10:36 ` dpdklab
2024-03-12 10:36 ` |FAILURE| " dpdklab
2024-03-12 10:36 ` |WARNING| " dpdklab
2024-03-12 10:37 ` |FAILURE| " dpdklab
2024-03-12 10:37 ` |SUCCESS| " dpdklab
2024-03-12 10:37 ` dpdklab
2024-03-12 10:37 ` |FAILURE| " dpdklab
2024-03-12 10:37 ` |SUCCESS| " dpdklab
2024-03-12 10:41 ` |FAILURE| " dpdklab
2024-03-12 10:41 ` dpdklab
2024-03-12 10:41 ` dpdklab
2024-03-12 10:43 ` dpdklab
2024-03-12 10:44 ` dpdklab [this message]
2024-03-12 10:50 ` dpdklab
2024-03-12 10:53 ` dpdklab
2024-03-12 10:58 ` dpdklab
2024-03-12 10:58 ` dpdklab
2024-03-12 10:58 ` |SUCCESS| " dpdklab
2024-03-12 10:59 ` |FAILURE| " dpdklab
2024-03-12 11:00 ` |SUCCESS| " dpdklab
2024-03-12 11:01 ` |FAILURE| " dpdklab
2024-03-12 11:06 ` dpdklab
2024-03-12 11:07 ` |SUCCESS| " dpdklab
2024-03-12 11:08 ` |FAILURE| " dpdklab
2024-03-12 11:08 ` |SUCCESS| " dpdklab
2024-03-12 11:09 ` |FAILURE| " dpdklab
2024-03-12 11:09 ` |SUCCESS| " dpdklab
2024-03-12 11:11 ` dpdklab
2024-03-12 11:15 ` |FAILURE| " dpdklab
2024-03-12 11:18 ` |SUCCESS| " dpdklab
2024-03-12 12:10 ` dpdklab
2024-03-12 12:24 ` dpdklab
2024-03-12 13:11 ` dpdklab
2024-03-15 20:07 ` dpdklab
2024-03-15 20:36 ` dpdklab

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=65f03200.050a0220.3afae.8d89SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=huangdengdui@huawei.com \
    --cc=test-report@dpdk.org \
    /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).