From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133482 [PATCH] ethdev: fix flow API support for P4-progr
Date: Fri, 27 Oct 2023 07:04:03 -0700 (PDT) [thread overview]
Message-ID: <653bc353.c80a0220.17fd0.2febSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133482
_Testing PASS_
Submitter: Wenjing Qiao <wenjing.qiao@intel.com>
Date: Friday, October 27 2023 09:17:43
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:656dfad43136ef43f4315ab6ed45b78b68c287a7
133482 --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
| CentOS Stream 9 | PASS |
+-----------------+----------------+
| Debian Buster | PASS |
+-----------------+----------------+
| Debian Bullseye | PASS |
+-----------------+----------------+
| Fedora 37 | PASS |
+-----------------+----------------+
| Fedora 38 | PASS |
+-----------------+----------------+
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
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28110/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-27 14:04 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 14:04 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-28 19:14 dpdklab
2023-10-27 15:06 dpdklab
2023-10-27 15:01 dpdklab
2023-10-27 14:32 dpdklab
2023-10-27 14:27 dpdklab
2023-10-27 14:26 dpdklab
2023-10-27 14:14 dpdklab
2023-10-27 14:13 dpdklab
2023-10-27 14:11 dpdklab
2023-10-27 14:11 dpdklab
2023-10-27 14:07 dpdklab
2023-10-27 14:07 dpdklab
2023-10-27 14:07 dpdklab
2023-10-27 14:02 dpdklab
2023-10-27 14:01 dpdklab
2023-10-27 14:01 dpdklab
2023-10-27 14:01 dpdklab
2023-10-27 14:00 dpdklab
2023-10-27 13:58 dpdklab
2023-10-27 13:57 dpdklab
2023-10-27 13:57 dpdklab
2023-10-27 13:57 dpdklab
2023-10-27 13:57 dpdklab
2023-10-27 13:56 dpdklab
2023-10-27 13:56 dpdklab
2023-10-27 13:56 dpdklab
2023-10-27 13:56 dpdklab
2023-10-27 13:56 dpdklab
2023-10-27 13:56 dpdklab
2023-10-27 13:55 dpdklab
2023-10-27 13:55 dpdklab
2023-10-27 13:54 dpdklab
2023-10-27 13:54 dpdklab
2023-10-27 13:54 dpdklab
2023-10-27 13:54 dpdklab
2023-10-27 13:54 dpdklab
2023-10-27 13:53 dpdklab
2023-10-27 13:53 dpdklab
2023-10-27 13:49 dpdklab
2023-10-27 13:48 dpdklab
2023-10-27 13:46 dpdklab
2023-10-27 13:46 dpdklab
2023-10-27 13:45 dpdklab
2023-10-27 13:38 dpdklab
2023-10-27 13:34 dpdklab
2023-10-27 13:33 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=653bc353.c80a0220.17fd0.2febSMTPIN_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).