From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw124119-124120 [PATCH] [v6, 2/2] ethdev: add flow matching of aggregated port
Date: Sat, 18 Feb 2023 10:33:58 +0000 (UTC) [thread overview]
Message-ID: <20230218103358.D08A5600AB@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2341 bytes --]
Test-Label: iol-x86_64-compile-testing
Test-Status: SUCCESS
http://dpdk.org/patch/124120
_Testing PASS_
Submitter: Jiawei Wang <jiaweiw@nvidia.com>
Date: Friday, February 17 2023 10:50:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8a3ef4b89e6dd0247355fdf3a77ff7ec1db28d8d
124119-124120 --> testing pass
Test environment and result as below:
+------------------+--------------------+
| Environment | dpdk_meson_compile |
+==================+====================+
| FreeBSD 13 | PASS |
+------------------+--------------------+
| RHEL 7 | PASS |
+------------------+--------------------+
| CentOS Stream 8 | PASS |
+------------------+--------------------+
| RHEL8 | PASS |
+------------------+--------------------+
| Ubuntu 22.04 | PASS |
+------------------+--------------------+
| Debian Bullseye | PASS |
+------------------+--------------------+
| Ubuntu 20.04 | PASS |
+------------------+--------------------+
| openSUSE Leap 15 | PASS |
+------------------+--------------------+
| Debian Buster | PASS |
+------------------+--------------------+
| CentOS Stream 9 | PASS |
+------------------+--------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: clang 14.0.5-1.fc36
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25435/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-18 10:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-18 10:33 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-24 23:20 dpdklab
2023-02-19 17:12 dpdklab
2023-02-17 11:56 dpdklab
2023-02-17 11:41 dpdklab
2023-02-17 11:37 dpdklab
2023-02-17 11:34 dpdklab
2023-02-17 11:34 dpdklab
2023-02-17 11:30 dpdklab
2023-02-17 11:28 dpdklab
2023-02-17 11:22 dpdklab
2023-02-17 11:22 dpdklab
2023-02-17 11:21 dpdklab
2023-02-17 11:19 dpdklab
[not found] <20230217105026.12927-3-jiaweiw@nvidia.com>
2023-02-17 10:39 ` |SUCCESS| pw124119-124120 [PATCH v6 " qemudev
2023-02-17 10:43 ` qemudev
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=20230218103358.D08A5600AB@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).