From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136213-136214 [PATCH] [v7,5/5] app/testpmd: stop forward
Date: Tue, 30 Jan 2024 00:40:46 -0800 (PST) [thread overview]
Message-ID: <65b8b60e.810a0220.1c929.41e9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136214
_Testing PASS_
Submitter: Huisong Li <lihuisong@huawei.com>
Date: Tuesday, January 30 2024 06:36:48
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:906d2c06b3cfc61620453c6909266fe771f8ccfb
136213-136214 --> testing pass
Test environment and result as below:
+-----------------+----------+
| Environment | abi_test |
+=================+==========+
| CentOS Stream 8 | PASS |
+-----------------+----------+
| CentOS Stream 9 | PASS |
+-----------------+----------+
| Debian Bullseye | PASS |
+-----------------+----------+
| Debian Buster | PASS |
+-----------------+----------+
| Fedora 37 | PASS |
+-----------------+----------+
| RHEL8 | 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 Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Fedora 38
Kernel: Depends on container host
Compiler: clang 16.0.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28987/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-30 8:40 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 8:40 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-30 12:55 dpdklab
2024-01-30 12:48 dpdklab
2024-01-30 12:39 dpdklab
2024-01-30 12:38 dpdklab
2024-01-30 12:26 dpdklab
2024-01-30 12:24 dpdklab
2024-01-30 12:24 dpdklab
2024-01-30 12:23 dpdklab
2024-01-30 12:22 dpdklab
2024-01-30 12:18 dpdklab
2024-01-30 12:17 dpdklab
2024-01-30 12:12 dpdklab
2024-01-30 12:01 dpdklab
2024-01-30 12:00 dpdklab
2024-01-30 11:59 dpdklab
2024-01-30 11:49 dpdklab
2024-01-30 10:48 dpdklab
2024-01-30 10:41 dpdklab
2024-01-30 10:35 dpdklab
2024-01-30 10:31 dpdklab
2024-01-30 10:25 dpdklab
2024-01-30 10:21 dpdklab
2024-01-30 10:20 dpdklab
2024-01-30 10:16 dpdklab
2024-01-30 10:16 dpdklab
2024-01-30 10:15 dpdklab
2024-01-30 10:15 dpdklab
2024-01-30 10:08 dpdklab
2024-01-30 9:56 dpdklab
2024-01-30 9:56 dpdklab
2024-01-30 9:54 dpdklab
2024-01-30 9:46 dpdklab
2024-01-30 9:44 dpdklab
2024-01-30 9:38 dpdklab
2024-01-30 9:19 dpdklab
2024-01-30 9:00 dpdklab
2024-01-30 8:59 dpdklab
2024-01-30 8:55 dpdklab
2024-01-30 8:52 dpdklab
2024-01-30 8:50 dpdklab
2024-01-30 8:45 dpdklab
2024-01-30 8:44 dpdklab
2024-01-30 8:44 dpdklab
2024-01-30 8:43 dpdklab
2024-01-30 8:42 dpdklab
2024-01-30 8:37 dpdklab
2024-01-30 8:35 dpdklab
2024-01-30 8:34 dpdklab
2024-01-30 8:32 dpdklab
2024-01-30 8:29 dpdklab
2024-01-30 8:29 dpdklab
2024-01-30 8:27 dpdklab
2024-01-30 8:19 dpdklab
2024-01-30 8:17 dpdklab
2024-01-30 8:06 dpdklab
2024-01-30 7:47 dpdklab
2024-01-30 7:46 dpdklab
2024-01-30 7:38 dpdklab
2024-01-30 7:31 dpdklab
2024-01-30 7:30 dpdklab
2024-01-30 7:29 dpdklab
2024-01-30 7:29 dpdklab
2024-01-30 7:29 dpdklab
2024-01-30 7:28 dpdklab
2024-01-30 7:24 dpdklab
2024-01-30 7:24 dpdklab
2024-01-30 7:22 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=65b8b60e.810a0220.1c929.41e9SMTPIN_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).