From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Gregory Etelson <getelson@nvidia.com>
Subject: |FAILURE| pw138464 [PATCH] net/mlx5: fix sync meter action
Date: Mon, 18 Mar 2024 13:35:48 -0700 (PDT) [thread overview]
Message-ID: <65f8a5a4.050a0220.23f94.7ba8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240318181045.272879-1-getelson@nvidia.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/138464
_Testing issues_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Monday, March 18 2024 18:10:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:478ca87cba284417f4575060ce02d94aa4991307
138464 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian 11 (arm) | FAIL |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
==== 20 line log output for Debian 11 (arm) (dpdk_unit_test): ====
102/112 DPDK:fast-tests / telemetry_data_autotest OK 0.18s
103/112 DPDK:fast-tests / telemetry_json_autotest OK 0.17s
104/112 DPDK:fast-tests / thash_autotest OK 0.18s
105/112 DPDK:fast-tests / threads_autotest OK 0.34s
106/112 DPDK:fast-tests / ticketlock_autotest OK 0.19s
107/112 DPDK:fast-tests / timer_autotest OK 2.50s
108/112 DPDK:fast-tests / trace_autotest OK 0.18s
109/112 DPDK:fast-tests / trace_autotest_with_traces OK 0.18s
110/112 DPDK:fast-tests / vdev_autotest OK 0.17s
111/112 DPDK:fast-tests / version_autotest OK 0.17s
112/112 DPDK:fast-tests / telemetry_all SKIP 0.01s exit status 77
Ok: 101
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 10
Timeout: 0
Full log written to /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/meson-logs/testlog.txt
==== End log output ====
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
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
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.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)
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29585/
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-18 20:35 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240318181045.272879-1-getelson@nvidia.com>
2024-03-18 17:49 ` |SUCCESS| " qemudev
2024-03-18 17:54 ` qemudev
2024-03-18 18:13 ` checkpatch
2024-03-18 19:03 ` 0-day Robot
2024-03-18 19:32 ` dpdklab
2024-03-18 19:33 ` dpdklab
2024-03-18 19:33 ` dpdklab
2024-03-18 19:35 ` dpdklab
2024-03-18 19:37 ` dpdklab
2024-03-18 19:37 ` dpdklab
2024-03-18 19:37 ` dpdklab
2024-03-18 19:38 ` dpdklab
2024-03-18 19:38 ` dpdklab
2024-03-18 19:55 ` dpdklab
2024-03-18 19:57 ` dpdklab
2024-03-18 19:57 ` dpdklab
2024-03-18 19:58 ` dpdklab
2024-03-18 19:58 ` dpdklab
2024-03-18 19:59 ` dpdklab
2024-03-18 19:59 ` dpdklab
2024-03-18 20:00 ` dpdklab
2024-03-18 20:00 ` dpdklab
2024-03-18 20:01 ` dpdklab
2024-03-18 20:01 ` dpdklab
2024-03-18 20:01 ` dpdklab
2024-03-18 20:02 ` dpdklab
2024-03-18 20:02 ` dpdklab
2024-03-18 20:02 ` dpdklab
2024-03-18 20:03 ` dpdklab
2024-03-18 20:06 ` dpdklab
2024-03-18 20:09 ` dpdklab
2024-03-18 20:10 ` dpdklab
2024-03-18 20:10 ` dpdklab
2024-03-18 20:14 ` dpdklab
2024-03-18 20:16 ` dpdklab
2024-03-18 20:16 ` dpdklab
2024-03-18 20:16 ` dpdklab
2024-03-18 20:17 ` dpdklab
2024-03-18 20:17 ` dpdklab
2024-03-18 20:17 ` dpdklab
2024-03-18 20:18 ` dpdklab
2024-03-18 20:18 ` dpdklab
2024-03-18 20:18 ` dpdklab
2024-03-18 20:18 ` dpdklab
2024-03-18 20:18 ` dpdklab
2024-03-18 20:19 ` dpdklab
2024-03-18 20:19 ` dpdklab
2024-03-18 20:19 ` dpdklab
2024-03-18 20:20 ` dpdklab
2024-03-18 20:24 ` |FAILURE| " dpdklab
2024-03-18 20:26 ` |SUCCESS| " dpdklab
2024-03-18 20:30 ` dpdklab
2024-03-18 20:31 ` dpdklab
2024-03-18 20:31 ` dpdklab
2024-03-18 20:31 ` |FAILURE| " dpdklab
2024-03-18 20:32 ` |SUCCESS| " dpdklab
2024-03-18 20:32 ` dpdklab
2024-03-18 20:33 ` dpdklab
2024-03-18 20:34 ` |FAILURE| " dpdklab
2024-03-18 20:35 ` |SUCCESS| " dpdklab
2024-03-18 20:35 ` dpdklab [this message]
2024-03-18 20:36 ` dpdklab
2024-03-18 20:36 ` |FAILURE| " dpdklab
2024-03-18 20:37 ` dpdklab
2024-03-18 20:37 ` |SUCCESS| " dpdklab
2024-03-18 20:37 ` dpdklab
2024-03-18 20:38 ` |FAILURE| " dpdklab
2024-03-18 20:39 ` dpdklab
2024-03-18 20:39 ` |SUCCESS| " dpdklab
2024-03-18 20:40 ` |FAILURE| " dpdklab
2024-03-18 20:40 ` |SUCCESS| " dpdklab
2024-03-18 20:41 ` |FAILURE| " dpdklab
2024-03-18 20:43 ` |SUCCESS| " dpdklab
2024-03-18 20:44 ` |FAILURE| " dpdklab
2024-03-18 20:45 ` |SUCCESS| " dpdklab
2024-03-18 21:20 ` dpdklab
2024-03-20 18:52 ` dpdklab
2024-03-20 19:16 ` 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=65f8a5a4.050a0220.23f94.7ba8SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=getelson@nvidia.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).