From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135818 [PATCH] doc: add testpmd latencystats option
Date: Tue, 09 Jan 2024 16:35:46 -0800 (PST) [thread overview]
Message-ID: <659de662.170a0220.8a836.7b01SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135818
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, January 09 2024 23:08:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6ef07151aac4b4d9601d547f94a996d1c71b3871
135818 --> testing pass
Test environment and result as below:
+-----------------------+--------------------+
| Environment | dpdk_meson_compile |
+=======================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+-----------------------+--------------------+
| CentOS Stream 9 (ARM) | PASS |
+-----------------------+--------------------+
| Fedora 38 (ARM) | PASS |
+-----------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28837/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-10 0:35 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 0:35 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-10 2:09 dpdklab
2024-01-10 2:05 dpdklab
2024-01-10 1:13 dpdklab
2024-01-10 1:05 dpdklab
2024-01-10 1:03 dpdklab
2024-01-10 1:02 dpdklab
2024-01-10 1:01 dpdklab
2024-01-10 0:56 dpdklab
2024-01-10 0:54 dpdklab
2024-01-10 0:54 dpdklab
2024-01-10 0:53 dpdklab
2024-01-10 0:53 dpdklab
2024-01-10 0:53 dpdklab
2024-01-10 0:53 dpdklab
2024-01-10 0:53 dpdklab
2024-01-10 0:52 dpdklab
2024-01-10 0:50 dpdklab
2024-01-10 0:48 dpdklab
2024-01-10 0:48 dpdklab
2024-01-10 0:47 dpdklab
2024-01-10 0:46 dpdklab
2024-01-10 0:45 dpdklab
2024-01-10 0:44 dpdklab
2024-01-10 0:44 dpdklab
2024-01-10 0:43 dpdklab
2024-01-10 0:43 dpdklab
2024-01-10 0:42 dpdklab
2024-01-10 0:42 dpdklab
2024-01-10 0:42 dpdklab
2024-01-10 0:41 dpdklab
2024-01-10 0:41 dpdklab
2024-01-10 0:41 dpdklab
2024-01-10 0:41 dpdklab
2024-01-10 0:40 dpdklab
2024-01-10 0:40 dpdklab
2024-01-10 0:40 dpdklab
2024-01-10 0:39 dpdklab
2024-01-10 0:39 dpdklab
2024-01-10 0:38 dpdklab
2024-01-10 0:38 dpdklab
2024-01-10 0:37 dpdklab
2024-01-10 0:37 dpdklab
2024-01-10 0:36 dpdklab
2024-01-10 0:36 dpdklab
2024-01-10 0:35 dpdklab
2024-01-10 0:35 dpdklab
2024-01-10 0:35 dpdklab
2024-01-10 0:35 dpdklab
2024-01-10 0:34 dpdklab
2024-01-10 0:34 dpdklab
2024-01-10 0:34 dpdklab
2024-01-10 0:34 dpdklab
2024-01-10 0:33 dpdklab
2024-01-10 0:33 dpdklab
2024-01-10 0:32 dpdklab
2024-01-10 0:32 dpdklab
2024-01-10 0:32 dpdklab
2024-01-10 0:32 dpdklab
2024-01-10 0:31 dpdklab
2024-01-10 0:31 dpdklab
2024-01-10 0:30 dpdklab
2024-01-10 0:19 dpdklab
2024-01-10 0:18 dpdklab
2024-01-10 0:17 dpdklab
2024-01-10 0:17 dpdklab
[not found] <20240109230849.6348-1-stephen@networkplumber.org>
2024-01-09 23:01 ` qemudev
2024-01-09 23:05 ` qemudev
2024-01-09 23:09 ` checkpatch
2024-01-10 0:26 ` 0-day Robot
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=659de662.170a0220.8a836.7b01SMTPIN_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).