From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Gregory Etelson <getelson@nvidia.com>
Subject: |SUCCESS| pw133996 [PATCH] app/testpmd: fix indirect action list par
Date: Wed, 08 Nov 2023 09:30:31 -0800 (PST) [thread overview]
Message-ID: <654bc5b7.050a0220.7072.db60SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133996
_Testing PASS_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Wednesday, November 08 2023 16:34:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2bbad8f974e00552d106c27e1d157a31179ab5ec
133996 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28287/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-11-08 17:30 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 17:30 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-09 12:01 dpdklab
2023-11-09 11:33 dpdklab
2023-11-08 22:00 dpdklab
2023-11-08 20:07 dpdklab
2023-11-08 18:21 dpdklab
2023-11-08 18:19 dpdklab
2023-11-08 18:18 dpdklab
2023-11-08 18:18 dpdklab
2023-11-08 18:15 dpdklab
2023-11-08 18:07 dpdklab
2023-11-08 18:07 dpdklab
2023-11-08 18:06 dpdklab
2023-11-08 18:06 dpdklab
2023-11-08 18:05 dpdklab
2023-11-08 18:04 dpdklab
2023-11-08 18:02 dpdklab
2023-11-08 18:01 dpdklab
2023-11-08 17:40 dpdklab
2023-11-08 17:40 dpdklab
2023-11-08 17:40 dpdklab
2023-11-08 17:40 dpdklab
2023-11-08 17:40 dpdklab
2023-11-08 17:40 dpdklab
2023-11-08 17:40 dpdklab
2023-11-08 17:40 dpdklab
2023-11-08 17:39 dpdklab
2023-11-08 17:35 dpdklab
2023-11-08 17:35 dpdklab
2023-11-08 17:35 dpdklab
2023-11-08 17:35 dpdklab
2023-11-08 17:35 dpdklab
2023-11-08 17:35 dpdklab
2023-11-08 17:35 dpdklab
2023-11-08 17:35 dpdklab
2023-11-08 17:34 dpdklab
2023-11-08 17:34 dpdklab
2023-11-08 17:34 dpdklab
2023-11-08 17:34 dpdklab
2023-11-08 17:30 dpdklab
2023-11-08 17:30 dpdklab
2023-11-08 17:30 dpdklab
2023-11-08 17:30 dpdklab
2023-11-08 17:30 dpdklab
2023-11-08 17:30 dpdklab
2023-11-08 17:30 dpdklab
2023-11-08 17:30 dpdklab
2023-11-08 17:30 dpdklab
2023-11-08 17:30 dpdklab
2023-11-08 17:26 dpdklab
2023-11-08 17:26 dpdklab
2023-11-08 17:15 dpdklab
2023-11-08 17:15 dpdklab
2023-11-08 17:14 dpdklab
2023-11-08 17:14 dpdklab
2023-11-08 17:14 dpdklab
2023-11-08 17:14 dpdklab
2023-11-08 17:13 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=654bc5b7.050a0220.7072.db60SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=getelson@nvidia.com \
--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).