From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136253 [PATCH] [v2] app/testpmd: support updating flow r
Date: Thu, 01 Feb 2024 02:41:11 -0800 (PST) [thread overview]
Message-ID: <65bb7547.050a0220.c9538.6e7dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136253
_Testing PASS_
Submitter: Oleksandr Kolomeiets <okl-plv@napatech.com>
Date: Thursday, February 01 2024 09:59:07
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8e5cbd3d1f6f077abdcb2ef4de027603ba9af5ca
136253 --> testing pass
Test environment and result as below:
+------------------+----------+
| Environment | abi_test |
+==================+==========+
| Ubuntu 22.04 | PASS |
+------------------+----------+
| CentOS Stream 8 | PASS |
+------------------+----------+
| RHEL8 | PASS |
+------------------+----------+
| openSUSE Leap 15 | PASS |
+------------------+----------+
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
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)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29012/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-01 10:41 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 10:41 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-01 13:55 dpdklab
2024-02-01 13:13 dpdklab
2024-02-01 11:54 dpdklab
2024-02-01 11:41 dpdklab
2024-02-01 11:26 dpdklab
2024-02-01 11:25 dpdklab
2024-02-01 11:23 dpdklab
2024-02-01 11:20 dpdklab
2024-02-01 11:18 dpdklab
2024-02-01 11:13 dpdklab
2024-02-01 11:08 dpdklab
2024-02-01 11:06 dpdklab
2024-02-01 11:00 dpdklab
2024-02-01 10:59 dpdklab
2024-02-01 10:57 dpdklab
2024-02-01 10:56 dpdklab
2024-02-01 10:54 dpdklab
2024-02-01 10:53 dpdklab
2024-02-01 10:53 dpdklab
2024-02-01 10:51 dpdklab
2024-02-01 10:50 dpdklab
2024-02-01 10:49 dpdklab
2024-02-01 10:49 dpdklab
2024-02-01 10:49 dpdklab
2024-02-01 10:47 dpdklab
2024-02-01 10:46 dpdklab
2024-02-01 10:46 dpdklab
2024-02-01 10:46 dpdklab
2024-02-01 10:44 dpdklab
2024-02-01 10:44 dpdklab
2024-02-01 10:44 dpdklab
2024-02-01 10:42 dpdklab
2024-02-01 10:42 dpdklab
2024-02-01 10:41 dpdklab
2024-02-01 10:41 dpdklab
2024-02-01 10:41 dpdklab
2024-02-01 10:39 dpdklab
2024-02-01 10:39 dpdklab
2024-02-01 10:38 dpdklab
2024-02-01 10:38 dpdklab
2024-02-01 10:38 dpdklab
2024-02-01 10:38 dpdklab
2024-02-01 10:38 dpdklab
2024-02-01 10:37 dpdklab
2024-02-01 10:37 dpdklab
2024-02-01 10:37 dpdklab
2024-02-01 10:36 dpdklab
2024-02-01 10:36 dpdklab
2024-02-01 10:36 dpdklab
2024-02-01 10:36 dpdklab
2024-02-01 10:35 dpdklab
2024-02-01 10:35 dpdklab
2024-02-01 10:35 dpdklab
2024-02-01 10:35 dpdklab
2024-02-01 10:35 dpdklab
2024-02-01 10:34 dpdklab
2024-02-01 10:34 dpdklab
2024-02-01 10:34 dpdklab
2024-02-01 10:34 dpdklab
2024-02-01 10:33 dpdklab
2024-02-01 10:33 dpdklab
2024-02-01 10: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=65bb7547.050a0220.c9538.6e7dSMTPIN_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).