From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw141998 [PATCH] eal/common: fix inconsistent representati
Date: Mon, 01 Jul 2024 15:46:24 -0700 (PDT) [thread overview]
Message-ID: <668331c0.050a0220.2826bb.63bbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240701200117.6349-1-shperetz@nvidia.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/141998
_Functional Testing PASS_
Submitter: Shani Peretz <shperetz@nvidia.com>
Date: Monday, July 01 2024 20:01:17
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c15902587b538ff02cfb0fbb4dd481f1503d936b
141998 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: Unknown
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| scatter | PASS |
+-----------------------------+--------+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: Unknown
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| scatter | PASS |
+-----------------------------+--------+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 11.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: Unknown
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30364/
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-07-01 22:46 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240701200117.6349-1-shperetz@nvidia.com>
2024-07-01 19:35 ` |SUCCESS| pw141998 [PATCH] eal/common: fix inconsistent representation of PCI numbers qemudev
2024-07-01 19:39 ` qemudev
2024-07-01 20:03 ` checkpatch
2024-07-01 21:05 ` 0-day Robot
2024-07-01 21:53 ` |SUCCESS| pw141998 [PATCH] eal/common: fix inconsistent representati dpdklab
2024-07-01 21:55 ` dpdklab
2024-07-01 22:13 ` dpdklab
2024-07-01 22:27 ` dpdklab
2024-07-01 22:36 ` dpdklab
2024-07-01 22:41 ` dpdklab
2024-07-01 22:46 ` |PENDING| " dpdklab
2024-07-01 22:46 ` dpdklab
2024-07-01 22:46 ` dpdklab [this message]
2024-07-01 22:46 ` dpdklab
2024-07-01 22:51 ` dpdklab
2024-07-01 22:52 ` dpdklab
2024-07-01 22:52 ` dpdklab
2024-07-01 22:52 ` dpdklab
2024-07-01 22:53 ` dpdklab
2024-07-01 22:53 ` dpdklab
2024-07-01 23:00 ` dpdklab
2024-07-01 23:01 ` dpdklab
2024-07-01 23:03 ` |SUCCESS| " dpdklab
2024-07-01 23:04 ` |PENDING| " dpdklab
2024-07-01 23:04 ` dpdklab
2024-07-01 23:05 ` dpdklab
2024-07-01 23:06 ` |SUCCESS| " dpdklab
2024-07-01 23:07 ` |PENDING| " dpdklab
2024-07-01 23:17 ` dpdklab
2024-07-01 23:21 ` dpdklab
2024-07-01 23:21 ` dpdklab
2024-07-01 23:22 ` dpdklab
2024-07-01 23:24 ` dpdklab
2024-07-01 23:30 ` dpdklab
2024-07-01 23:38 ` |SUCCESS| " dpdklab
2024-07-01 23:38 ` dpdklab
2024-07-01 23:39 ` |PENDING| " dpdklab
2024-07-02 0:03 ` dpdklab
2024-07-02 0:23 ` dpdklab
2024-07-02 0:35 ` dpdklab
2024-07-02 0:36 ` dpdklab
2024-07-02 0:42 ` dpdklab
2024-07-02 0:44 ` dpdklab
2024-07-02 0:46 ` dpdklab
2024-07-02 0:46 ` dpdklab
2024-07-02 0:50 ` dpdklab
2024-07-02 0:54 ` dpdklab
2024-07-02 0:54 ` dpdklab
2024-07-02 0:57 ` dpdklab
2024-07-02 1:01 ` dpdklab
2024-07-02 1:03 ` dpdklab
2024-07-02 1:03 ` dpdklab
2024-07-02 1:07 ` dpdklab
2024-07-02 1:09 ` dpdklab
2024-07-02 1:12 ` dpdklab
2024-07-02 1:14 ` dpdklab
2024-07-02 1:16 ` dpdklab
2024-07-02 1:20 ` dpdklab
2024-07-02 1:20 ` dpdklab
2024-07-02 1:24 ` dpdklab
2024-07-02 1:24 ` dpdklab
2024-07-02 1:25 ` dpdklab
2024-07-02 1:28 ` dpdklab
2024-07-02 1:29 ` dpdklab
2024-07-02 1:30 ` dpdklab
2024-07-02 1:31 ` dpdklab
2024-07-02 1:35 ` |SUCCESS| " dpdklab
2024-07-02 1:35 ` |PENDING| " dpdklab
2024-07-02 1:37 ` dpdklab
2024-07-02 1:37 ` dpdklab
2024-07-02 1:39 ` dpdklab
2024-07-02 1:40 ` dpdklab
2024-07-02 1:44 ` dpdklab
2024-07-02 1:44 ` dpdklab
2024-07-02 1:48 ` dpdklab
2024-07-02 1:53 ` dpdklab
2024-07-02 2:05 ` |SUCCESS| " dpdklab
2024-07-02 2:45 ` |PENDING| " dpdklab
2024-07-02 2:58 ` dpdklab
2024-07-02 3:00 ` dpdklab
2024-07-02 3:04 ` dpdklab
2024-07-02 3:07 ` dpdklab
2024-07-02 3:14 ` dpdklab
2024-07-02 3:14 ` dpdklab
2024-07-02 3:29 ` dpdklab
2024-07-02 3:43 ` dpdklab
2024-07-02 3:58 ` dpdklab
2024-07-02 4:13 ` dpdklab
2024-07-02 4:17 ` dpdklab
2024-07-02 4:27 ` dpdklab
2024-07-02 4:33 ` dpdklab
2024-07-02 4:34 ` dpdklab
2024-07-02 4:36 ` dpdklab
2024-07-02 4:40 ` dpdklab
2024-07-02 4:41 ` dpdklab
2024-07-02 4:44 ` dpdklab
2024-07-02 4:52 ` dpdklab
2024-07-02 4:58 ` dpdklab
2024-07-02 5:00 ` dpdklab
2024-07-02 5:01 ` |SUCCESS| " dpdklab
2024-07-02 5:27 ` |PENDING| " dpdklab
2024-07-02 5:36 ` dpdklab
2024-07-02 5:49 ` dpdklab
2024-07-02 5:56 ` dpdklab
2024-07-02 6:06 ` dpdklab
2024-07-02 6:07 ` dpdklab
2024-07-02 6:43 ` |SUCCESS| " dpdklab
2024-07-02 7:08 ` dpdklab
2024-07-02 15:13 ` dpdklab
2024-07-02 15:27 ` 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=668331c0.050a0220.2826bb.63bbSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).