From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Jingjing Wu <jingjing.wu@intel.com>
Subject: |FAILURE| pw138477 [PATCH] graph: fix head move when graph walk in m
Date: Tue, 19 Mar 2024 00:56:45 -0700 (PDT) [thread overview]
Message-ID: <65f9453d.0c0a0220.265ef.b586SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240319141454.3275543-1-jingjing.wu@intel.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/138477
_Testing issues_
Submitter: Jingjing Wu <jingjing.wu@intel.com>
Date: Tuesday, March 19 2024 14:14:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
138477 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Debian 11 (arm) | FAIL |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Bullseye | FAIL |
+---------------------+----------------+
| CentOS Stream 8 | FAIL |
+---------------------+----------------+
| Fedora 37 | FAIL |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | FAIL |
+---------------------+----------------+
| Fedora 38 | FAIL |
+---------------------+----------------+
| Ubuntu 22.04 | FAIL |
+---------------------+----------------+
| Ubuntu 20.04 | FAIL |
+---------------------+----------------+
| RHEL8 | FAIL |
+---------------------+----------------+
| openSUSE Leap 15 | FAIL |
+---------------------+----------------+
==== 20 line log output for openSUSE Leap 15 (dpdk_unit_test): ====
101/111 DPDK:fast-tests / telemetry_data_autotest OK 0.17 s
102/111 DPDK:fast-tests / telemetry_json_autotest OK 0.17 s
103/111 DPDK:fast-tests / thash_autotest OK 0.22 s
104/111 DPDK:fast-tests / threads_autotest OK 0.37 s
105/111 DPDK:fast-tests / ticketlock_autotest OK 0.22 s
106/111 DPDK:fast-tests / timer_autotest OK 2.47 s
107/111 DPDK:fast-tests / trace_autotest OK 0.22 s
108/111 DPDK:fast-tests / trace_autotest_with_traces OK 0.22 s
109/111 DPDK:fast-tests / vdev_autotest OK 0.17 s
110/111 DPDK:fast-tests / version_autotest OK 0.17 s
111/111 DPDK:fast-tests / telemetry_all SKIP 0.01 s
Ok: 99
Expected Fail: 0
Fail: 0
Unexpected Pass: 0
Skipped: 11
Timeout: 1
Full log written to /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/meson-logs/testlog.txt
==== End log output ====
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.6
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29590/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-19 7:56 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240319141454.3275543-1-jingjing.wu@intel.com>
2024-03-19 5:59 ` |SUCCESS| pw138477 [PATCH] graph: fix head move when graph walk in mcore dispatch qemudev
2024-03-19 6:05 ` |FAILURE| " qemudev
2024-03-19 6:23 ` |SUCCESS| " checkpatch
2024-03-19 7:10 ` |SUCCESS| pw138477 [PATCH] graph: fix head move when graph walk in m dpdklab
2024-03-19 7:10 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:11 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:12 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:13 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:14 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:15 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:16 ` dpdklab
2024-03-19 7:17 ` dpdklab
2024-03-19 7:18 ` dpdklab
2024-03-19 7:19 ` |FAILURE| " dpdklab
2024-03-19 7:20 ` |SUCCESS| " dpdklab
2024-03-19 7:20 ` |FAILURE| " dpdklab
2024-03-19 7:20 ` |SUCCESS| " dpdklab
2024-03-19 7:22 ` dpdklab
2024-03-19 7:22 ` dpdklab
2024-03-19 7:23 ` |FAILURE| " dpdklab
2024-03-19 7:23 ` |SUCCESS| " dpdklab
2024-03-19 7:23 ` |FAILURE| pw138477 [PATCH] graph: fix head move when graph walk in mcore dispatch 0-day Robot
2024-03-19 7:24 ` |FAILURE| pw138477 [PATCH] graph: fix head move when graph walk in m dpdklab
2024-03-19 7:26 ` dpdklab
2024-03-19 7:27 ` dpdklab
2024-03-19 7:29 ` dpdklab
2024-03-19 7:30 ` |SUCCESS| " dpdklab
2024-03-19 7:30 ` dpdklab
2024-03-19 7:32 ` |FAILURE| " dpdklab
2024-03-19 7:32 ` dpdklab
2024-03-19 7:33 ` dpdklab
2024-03-19 7:34 ` |SUCCESS| " dpdklab
2024-03-19 7:41 ` |FAILURE| " dpdklab
2024-03-19 7:41 ` dpdklab
2024-03-19 7:42 ` dpdklab
2024-03-19 7:46 ` dpdklab
2024-03-19 7:47 ` dpdklab
2024-03-19 7:47 ` dpdklab
2024-03-19 7:56 ` dpdklab [this message]
2024-03-19 7:57 ` dpdklab
2024-03-19 8:03 ` dpdklab
2024-03-19 8:25 ` |SUCCESS| " dpdklab
2024-03-21 4:18 ` dpdklab
2024-03-21 5:18 ` 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=65f9453d.0c0a0220.265ef.b586SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=jingjing.wu@intel.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).