From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142511-142512 [PATCH] [2/2] doc: remove use of -n 4 opti
Date: Fri, 19 Jul 2024 08:29:43 -0700 (PDT) [thread overview]
Message-ID: <669a8667.170a0220.3c0876.067aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240718184326.21375-2-stephen@networkplumber.org>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142512
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, July 18 2024 18:43:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084
142511-142512 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#169084
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/30556/
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-19 15:29 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240718184326.21375-2-stephen@networkplumber.org>
2024-07-18 18:17 ` |SUCCESS| pw142511-142512 [PATCH 2/2] doc: remove use of -n 4 option in documentation qemudev
2024-07-18 18:22 ` qemudev
2024-07-18 18:44 ` |WARNING| pw142512 " checkpatch
2024-07-18 19:43 ` |SUCCESS| " 0-day Robot
2024-07-19 11:16 ` |SUCCESS| pw142511-142512 [PATCH] [2/2] doc: remove use of -n 4 opti dpdklab
2024-07-19 11:20 ` dpdklab
2024-07-19 11:24 ` dpdklab
2024-07-19 11:24 ` dpdklab
2024-07-19 11:37 ` dpdklab
2024-07-19 11:37 ` dpdklab
2024-07-19 11:39 ` dpdklab
2024-07-19 11:50 ` dpdklab
2024-07-19 12:27 ` |PENDING| " dpdklab
2024-07-19 12:35 ` |SUCCESS| " dpdklab
2024-07-19 12:39 ` dpdklab
2024-07-19 13:10 ` dpdklab
2024-07-19 13:14 ` |PENDING| " dpdklab
2024-07-19 13:26 ` dpdklab
2024-07-19 13:26 ` dpdklab
2024-07-19 13:27 ` dpdklab
2024-07-19 13:28 ` dpdklab
2024-07-19 13:31 ` dpdklab
2024-07-19 13:32 ` dpdklab
2024-07-19 13:34 ` dpdklab
2024-07-19 13:34 ` dpdklab
2024-07-19 13:36 ` dpdklab
2024-07-19 13:36 ` dpdklab
2024-07-19 13:36 ` dpdklab
2024-07-19 13:40 ` dpdklab
2024-07-19 13:40 ` dpdklab
2024-07-19 13:41 ` dpdklab
2024-07-19 13:42 ` |SUCCESS| " dpdklab
2024-07-19 13:43 ` |PENDING| " dpdklab
2024-07-19 13:44 ` dpdklab
2024-07-19 13:45 ` dpdklab
2024-07-19 13:47 ` dpdklab
2024-07-19 13:48 ` dpdklab
2024-07-19 13:49 ` dpdklab
2024-07-19 13:50 ` dpdklab
2024-07-19 13:50 ` dpdklab
2024-07-19 13:50 ` dpdklab
2024-07-19 13:52 ` dpdklab
2024-07-19 13:54 ` dpdklab
2024-07-19 14:01 ` dpdklab
2024-07-19 14:02 ` dpdklab
2024-07-19 14:02 ` dpdklab
2024-07-19 14:06 ` |SUCCESS| " dpdklab
2024-07-19 14:08 ` |PENDING| " dpdklab
2024-07-19 14:13 ` dpdklab
2024-07-19 14:14 ` dpdklab
2024-07-19 14:14 ` dpdklab
2024-07-19 14:15 ` dpdklab
2024-07-19 14:15 ` dpdklab
2024-07-19 14:16 ` dpdklab
2024-07-19 14:18 ` dpdklab
2024-07-19 14:19 ` dpdklab
2024-07-19 14:19 ` dpdklab
2024-07-19 14:21 ` dpdklab
2024-07-19 14:23 ` dpdklab
2024-07-19 14:23 ` dpdklab
2024-07-19 14:24 ` dpdklab
2024-07-19 14:24 ` dpdklab
2024-07-19 14:26 ` dpdklab
2024-07-19 14:28 ` dpdklab
2024-07-19 14:28 ` dpdklab
2024-07-19 14:28 ` dpdklab
2024-07-19 14:28 ` dpdklab
2024-07-19 14:29 ` dpdklab
2024-07-19 14:29 ` dpdklab
2024-07-19 14:30 ` dpdklab
2024-07-19 14:30 ` dpdklab
2024-07-19 14:30 ` |SUCCESS| " dpdklab
2024-07-19 14:31 ` |PENDING| " dpdklab
2024-07-19 14:31 ` dpdklab
2024-07-19 14:32 ` dpdklab
2024-07-19 14:32 ` dpdklab
2024-07-19 14:33 ` dpdklab
2024-07-19 14:33 ` dpdklab
2024-07-19 14:35 ` |SUCCESS| " dpdklab
2024-07-19 14:36 ` |PENDING| " dpdklab
2024-07-19 14:37 ` dpdklab
2024-07-19 14:38 ` dpdklab
2024-07-19 14:39 ` |SUCCESS| " dpdklab
2024-07-19 14:40 ` |PENDING| " dpdklab
2024-07-19 14:40 ` dpdklab
2024-07-19 14:42 ` dpdklab
2024-07-19 14:42 ` dpdklab
2024-07-19 14:46 ` dpdklab
2024-07-19 14:51 ` |SUCCESS| " dpdklab
2024-07-19 14:58 ` dpdklab
2024-07-19 15:29 ` dpdklab [this message]
2024-07-19 15:31 ` |PENDING| " dpdklab
2024-07-19 15:32 ` dpdklab
2024-07-19 15:32 ` dpdklab
2024-07-19 15:33 ` dpdklab
2024-07-19 15:34 ` dpdklab
2024-07-19 15:35 ` dpdklab
2024-07-19 15:36 ` dpdklab
2024-07-19 15:38 ` dpdklab
2024-07-19 15:38 ` dpdklab
2024-07-19 15:39 ` dpdklab
2024-07-19 15:41 ` |SUCCESS| " dpdklab
2024-07-19 15:42 ` |PENDING| " dpdklab
2024-07-19 15:48 ` dpdklab
2024-07-19 15:49 ` dpdklab
2024-07-19 15:49 ` dpdklab
2024-07-19 15:50 ` dpdklab
2024-07-19 15:51 ` dpdklab
2024-07-19 15:52 ` dpdklab
2024-07-19 15:52 ` dpdklab
2024-07-19 15:55 ` dpdklab
2024-07-19 16:01 ` dpdklab
2024-07-19 16:04 ` |SUCCESS| " dpdklab
2024-07-19 16:05 ` |PENDING| " dpdklab
2024-07-19 16:12 ` |SUCCESS| " dpdklab
2024-07-19 22:25 ` 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=669a8667.170a0220.3c0876.067aSMTPIN_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).