From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |SUCCESS| pw123898 [PATCH] net/sfc: enforce fate action in transfer flow rules
Date: Thu, 16 Feb 2023 21:03:51 +0000 (UTC) [thread overview]
Message-ID: <20230216210351.BEDF1600AB@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2350 bytes --]
Test-Label: iol-x86_64-compile-testing
Test-Status: SUCCESS
http://dpdk.org/patch/123898
_Testing PASS_
Submitter: Ivan Malov <ivan.malov@arknetworks.am>
Date: Tuesday, February 14 2023 13:12:47
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:a2a8cb4251308ce5ccbe391576fe6483c3adbc4c
123898 --> testing pass
Test environment and result as below:
+------------------+--------------------+
| Environment | dpdk_meson_compile |
+==================+====================+
| FreeBSD 13 | PASS |
+------------------+--------------------+
| CentOS Stream 8 | PASS |
+------------------+--------------------+
| Debian Buster | PASS |
+------------------+--------------------+
| CentOS Stream 9 | PASS |
+------------------+--------------------+
| RHEL 7 | PASS |
+------------------+--------------------+
| Debian Bullseye | PASS |
+------------------+--------------------+
| Ubuntu 22.04 | PASS |
+------------------+--------------------+
| RHEL8 | PASS |
+------------------+--------------------+
| openSUSE Leap 15 | PASS |
+------------------+--------------------+
| Ubuntu 20.04 | PASS |
+------------------+--------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
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
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)
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: clang 14.0.5-1.fc36
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25392/
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-16 21:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 21:03 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-18 18:35 dpdklab
2023-02-15 11:36 dpdklab
2023-02-15 11:36 dpdklab
2023-02-15 11:31 dpdklab
2023-02-15 11:15 dpdklab
2023-02-15 11:11 dpdklab
2023-02-15 11:10 dpdklab
2023-02-15 11:09 dpdklab
2023-02-15 11:07 dpdklab
2023-02-15 11:06 dpdklab
2023-02-15 10:55 dpdklab
2023-02-15 10:52 dpdklab
2023-02-15 10:50 dpdklab
2023-02-15 10:40 dpdklab
2023-02-15 10:36 dpdklab
2023-02-15 10:21 dpdklab
2023-02-15 10:13 dpdklab
2023-02-15 10:12 dpdklab
2023-02-15 10:10 dpdklab
2023-02-15 10:07 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=20230216210351.BEDF1600AB@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=ferruh.yigit@amd.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).