From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131098 [PATCH] [1/1] drivers/net: fix checking for Tx si
Date: Sat, 02 Sep 2023 03:22:35 -0700 (PDT) [thread overview]
Message-ID: <64f30ceb.020a0220.72d28.b9b5SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131098
_Testing PASS_
Submitter: Min Zhou <zhoumin@loongson.cn>
Date: Saturday, September 02 2023 09:37:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:799d56f1192d72872e63fbb3d2c7f776b7ae89b0
131098 --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| Debian Buster | PASS |
+-----------------+----------------+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
| CentOS Stream 9 | PASS |
+-----------------+----------------+
| Fedora 37 | PASS |
+-----------------+----------------+
| Debian Bullseye | PASS |
+-----------------+----------------+
| RHEL8 | PASS |
+-----------------+----------------+
| Fedora 38 | PASS |
+-----------------+----------------+
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
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
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
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: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27508/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-02 10:22 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-02 10:22 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-06 5:07 dpdklab
2023-09-06 4:56 dpdklab
2023-09-06 4:51 dpdklab
2023-09-06 4:48 dpdklab
2023-09-05 14:10 dpdklab
2023-09-05 14:04 dpdklab
2023-09-05 14:01 dpdklab
2023-09-02 11:32 dpdklab
2023-09-02 10:39 dpdklab
2023-09-02 10:35 dpdklab
2023-09-02 10:31 dpdklab
2023-09-02 10:31 dpdklab
2023-09-02 10:31 dpdklab
2023-09-02 10:30 dpdklab
2023-09-02 10:28 dpdklab
2023-09-02 10:28 dpdklab
2023-09-02 10:27 dpdklab
2023-09-02 10:25 dpdklab
2023-09-02 10:25 dpdklab
2023-09-02 10:23 dpdklab
2023-09-02 10:22 dpdklab
2023-09-02 10:22 dpdklab
2023-09-02 10:19 dpdklab
2023-09-02 10:19 dpdklab
2023-09-02 10:19 dpdklab
2023-09-02 10:19 dpdklab
2023-09-02 10:19 dpdklab
2023-09-02 10:19 dpdklab
2023-09-02 10:18 dpdklab
2023-09-02 10:18 dpdklab
2023-09-02 10:18 dpdklab
2023-09-02 10:18 dpdklab
2023-09-02 10:18 dpdklab
2023-09-02 10:18 dpdklab
2023-09-02 10:18 dpdklab
2023-09-02 10:18 dpdklab
2023-09-02 10:18 dpdklab
2023-09-02 10:18 dpdklab
2023-09-02 10:17 dpdklab
2023-09-02 10:16 dpdklab
2023-09-02 10:15 dpdklab
2023-09-02 10:14 dpdklab
2023-09-02 10:13 dpdklab
2023-09-02 10:12 dpdklab
2023-09-02 10:12 dpdklab
2023-09-02 10:11 dpdklab
2023-09-02 10:11 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=64f30ceb.020a0220.72d28.b9b5SMTPIN_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).