From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw154914 [PATCH] [v3] test/argparse: change initialization
Date: Thu, 03 Jul 2025 18:17:06 -0700 (PDT) [thread overview]
Message-ID: <68672b92.050a0220.a7ee6.1283SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250701154202.237442-1-stephen@networkplumber.org>
Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/154914
_Performance Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, July 01 2025 15:41:46
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:70c2297528e7c7789af452f78de1932e9a20c8a2
154914 --> performance testing pass
Upstream job id: Template-DTS-Pipeline#234944
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Fail/Total: 0/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | 0.1% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | 0.0% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33557/
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:[~2025-07-04 1:17 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250701154202.237442-1-stephen@networkplumber.org>
2025-07-01 15:13 ` |SUCCESS| pw154914 [PATCH v3] test/argparse: change initialization to workaround LTO qemudev
2025-07-01 15:17 ` qemudev
2025-07-01 15:40 ` |WARNING| " checkpatch
2025-07-01 17:03 ` |SUCCESS| " 0-day Robot
2025-07-02 21:38 ` |SUCCESS| pw154914 [PATCH] [v3] test/argparse: change initialization dpdklab
2025-07-02 22:07 ` dpdklab
2025-07-03 0:07 ` |PENDING| " dpdklab
2025-07-03 0:17 ` |SUCCESS| " dpdklab
2025-07-03 0:24 ` |PENDING| " dpdklab
2025-07-03 0:29 ` dpdklab
2025-07-03 2:03 ` |SUCCESS| " dpdklab
2025-07-03 2:24 ` |PENDING| " dpdklab
2025-07-03 3:50 ` dpdklab
2025-07-03 4:11 ` dpdklab
2025-07-03 4:15 ` |FAILURE| " dpdklab
2025-07-03 4:15 ` dpdklab
2025-07-03 23:20 ` |PENDING| " dpdklab
2025-07-03 23:28 ` |FAILURE| " dpdklab
2025-07-03 23:30 ` |PENDING| " dpdklab
2025-07-03 23:34 ` dpdklab
2025-07-03 23:36 ` |SUCCESS| " dpdklab
2025-07-03 23:37 ` dpdklab
2025-07-03 23:37 ` |PENDING| " dpdklab
2025-07-03 23:40 ` |SUCCESS| " dpdklab
2025-07-03 23:59 ` dpdklab
2025-07-04 1:17 ` dpdklab [this message]
2025-07-04 1:21 ` dpdklab
2025-07-04 1:28 ` |PENDING| " dpdklab
2025-07-04 1:43 ` |FAILURE| " dpdklab
2025-07-04 1:48 ` |SUCCESS| " dpdklab
2025-07-04 1:55 ` dpdklab
2025-07-04 1:59 ` dpdklab
2025-07-04 2:24 ` dpdklab
2025-07-04 2:39 ` |FAILURE| " dpdklab
2025-07-04 3:07 ` |SUCCESS| " dpdklab
2025-07-04 3:42 ` |WARNING| " dpdklab
2025-07-04 3:43 ` dpdklab
2025-07-04 6:15 ` |SUCCESS| " dpdklab
2025-07-04 8:41 ` dpdklab
2025-07-04 8:41 ` dpdklab
2025-07-04 9:32 ` 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=68672b92.050a0220.a7ee6.1283SMTPIN_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).