From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142652-142654 [PATCH] [v2,3/3] test-pmd: add more packet
Date: Tue, 23 Jul 2024 02:11:30 -0700 (PDT) [thread overview]
Message-ID: <669f73c2.0d0a0220.fa8a8.50c8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240723024537.980016-4-stephen@networkplumber.org>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142654
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, July 23 2024 02:44:12
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:82baecc069d9247c6890677d84481c1cdff84ecb
142652-142654 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#169876
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-100-generic x86_64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| scatter | PASS |
+-----------------+--------+
| unit_tests_mbuf | PASS |
+-----------------+--------+
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30585/
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-23 9:32 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240723024537.980016-4-stephen@networkplumber.org>
2024-07-23 2:20 ` |SUCCESS| pw142652-142654 [PATCH v2 3/3] test-pmd: add more packet verbose decode options qemudev
2024-07-23 2:24 ` qemudev
2024-07-23 2:47 ` |WARNING| pw142654 " checkpatch
2024-07-23 3:43 ` |FAILURE| " 0-day Robot
2024-07-23 5:44 ` |PENDING| pw142652-142654 [PATCH] [v2,3/3] test-pmd: add more packet dpdklab
2024-07-23 5:57 ` |SUCCESS| " dpdklab
2024-07-23 5:59 ` dpdklab
2024-07-23 6:00 ` |PENDING| " dpdklab
2024-07-23 6:07 ` |SUCCESS| " dpdklab
2024-07-23 6:09 ` |PENDING| " dpdklab
2024-07-23 6:17 ` |SUCCESS| " dpdklab
2024-07-23 6:21 ` dpdklab
2024-07-23 6:21 ` |PENDING| " dpdklab
2024-07-23 6:22 ` dpdklab
2024-07-23 6:22 ` dpdklab
2024-07-23 6:24 ` dpdklab
2024-07-23 6:25 ` dpdklab
2024-07-23 6:27 ` dpdklab
2024-07-23 6:29 ` |SUCCESS| " dpdklab
2024-07-23 6:31 ` |PENDING| " dpdklab
2024-07-23 6:37 ` dpdklab
2024-07-23 6:43 ` dpdklab
2024-07-23 6:44 ` dpdklab
2024-07-23 6:46 ` |SUCCESS| " dpdklab
2024-07-23 6:47 ` |PENDING| " dpdklab
2024-07-23 6:53 ` dpdklab
2024-07-23 6:56 ` |SUCCESS| " dpdklab
2024-07-23 7:09 ` dpdklab
2024-07-23 7:11 ` |PENDING| " dpdklab
2024-07-23 7:19 ` |SUCCESS| " dpdklab
2024-07-23 7:22 ` |FAILURE| " dpdklab
2024-07-23 7:23 ` dpdklab
2024-07-23 7:24 ` dpdklab
2024-07-23 7:25 ` dpdklab
2024-07-23 7:26 ` |PENDING| " dpdklab
2024-07-23 7:26 ` |FAILURE| " dpdklab
2024-07-23 7:27 ` |PENDING| " dpdklab
2024-07-23 7:29 ` dpdklab
2024-07-23 7:31 ` dpdklab
2024-07-23 7:33 ` dpdklab
2024-07-23 7:35 ` dpdklab
2024-07-23 7:35 ` dpdklab
2024-07-23 7:38 ` dpdklab
2024-07-23 7:39 ` dpdklab
2024-07-23 7:41 ` |FAILURE| " dpdklab
2024-07-23 7:41 ` |PENDING| " dpdklab
2024-07-23 7:42 ` dpdklab
2024-07-23 7:44 ` dpdklab
2024-07-23 7:47 ` dpdklab
2024-07-23 7:51 ` |FAILURE| " dpdklab
2024-07-23 7:52 ` |PENDING| " dpdklab
2024-07-23 7:54 ` dpdklab
2024-07-23 7:55 ` |SUCCESS| " dpdklab
2024-07-23 7:55 ` |PENDING| " dpdklab
2024-07-23 7:55 ` |FAILURE| " dpdklab
2024-07-23 8:00 ` |PENDING| " dpdklab
2024-07-23 8:02 ` dpdklab
2024-07-23 8:06 ` |FAILURE| " dpdklab
2024-07-23 8:15 ` |PENDING| " dpdklab
2024-07-23 8:16 ` dpdklab
2024-07-23 8:19 ` dpdklab
2024-07-23 8:21 ` dpdklab
2024-07-23 8:25 ` dpdklab
2024-07-23 8:25 ` dpdklab
2024-07-23 8:28 ` dpdklab
2024-07-23 8:29 ` dpdklab
2024-07-23 8:34 ` dpdklab
2024-07-23 8:44 ` dpdklab
2024-07-23 8:46 ` |FAILURE| " dpdklab
2024-07-23 8:49 ` dpdklab
2024-07-23 8:50 ` |PENDING| " dpdklab
2024-07-23 8:54 ` dpdklab
2024-07-23 8:55 ` dpdklab
2024-07-23 8:56 ` |SUCCESS| " dpdklab
2024-07-23 8:58 ` |FAILURE| " dpdklab
2024-07-23 8:59 ` |PENDING| " dpdklab
2024-07-23 8:59 ` |FAILURE| " dpdklab
2024-07-23 9:01 ` |SUCCESS| " dpdklab
2024-07-23 9:02 ` |FAILURE| " dpdklab
2024-07-23 9:04 ` dpdklab
2024-07-23 9:04 ` dpdklab
2024-07-23 9:06 ` |SUCCESS| " dpdklab
2024-07-23 9:08 ` |FAILURE| " dpdklab
2024-07-23 9:10 ` dpdklab
2024-07-23 9:11 ` dpdklab [this message]
2024-07-23 9:13 ` dpdklab
2024-07-23 9:17 ` dpdklab
2024-07-23 9:21 ` dpdklab
2024-07-23 9:22 ` |PENDING| " dpdklab
2024-07-23 9:22 ` |FAILURE| " dpdklab
2024-07-23 9:22 ` |PENDING| " dpdklab
2024-07-23 9:23 ` |FAILURE| " dpdklab
2024-07-23 9:26 ` dpdklab
2024-07-23 9:28 ` dpdklab
2024-07-23 9:29 ` dpdklab
2024-07-23 9:29 ` dpdklab
2024-07-23 9:29 ` dpdklab
2024-07-23 9:30 ` |SUCCESS| " dpdklab
2024-07-23 9:34 ` |FAILURE| " dpdklab
2024-07-23 9:37 ` dpdklab
2024-07-23 9:41 ` dpdklab
2024-07-23 9:44 ` dpdklab
2024-07-23 9:44 ` dpdklab
2024-07-23 9:50 ` dpdklab
2024-07-23 9:50 ` dpdklab
2024-07-23 9:55 ` dpdklab
2024-07-23 9:58 ` dpdklab
2024-07-23 9:59 ` dpdklab
2024-07-23 10:03 ` dpdklab
2024-07-23 10:07 ` dpdklab
2024-07-23 10:08 ` |SUCCESS| " dpdklab
2024-07-23 10:11 ` |FAILURE| " dpdklab
2024-07-23 10:12 ` |SUCCESS| " dpdklab
2024-07-23 10:15 ` dpdklab
2024-07-23 10:16 ` |FAILURE| " dpdklab
2024-07-24 3:24 ` |SUCCESS| " 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=669f73c2.0d0a0220.fa8a8.50c8SMTPIN_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).