From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133375-133374 [PATCH] [v7,10/10] net/mlx5: support indir
Date: Thu, 26 Oct 2023 05:09:06 -0700 (PDT) [thread overview]
Message-ID: <653a56e2.050a0220.62815.6cdfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133374
_Testing PASS_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Thursday, October 26 2023 07:12:29
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2a0557d1ea21c3f63a212385348c97c414970e81
133375-133374 --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| CentOS Stream 9 | PASS |
+------------------+----------------+
| CentOS Stream 8 | PASS |
+------------------+----------------+
| Debian Bullseye | PASS |
+------------------+----------------+
| Debian Buster | PASS |
+------------------+----------------+
| Fedora 37 | PASS |
+------------------+----------------+
| Fedora 38 | PASS |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
| RHEL8 | PASS |
+------------------+----------------+
| Ubuntu 20.04 | PASS |
+------------------+----------------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
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
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
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 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28080/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-26 12:09 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 12:09 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-28 4:11 dpdklab
2023-10-26 22:22 dpdklab
2023-10-26 22:08 dpdklab
2023-10-26 21:40 dpdklab
2023-10-26 13:13 dpdklab
2023-10-26 13:07 dpdklab
2023-10-26 12:44 dpdklab
2023-10-26 12:29 dpdklab
2023-10-26 12:19 dpdklab
2023-10-26 12:16 dpdklab
2023-10-26 12:12 dpdklab
2023-10-26 12:11 dpdklab
2023-10-26 12:08 dpdklab
2023-10-26 12:07 dpdklab
2023-10-26 12:03 dpdklab
2023-10-26 12:02 dpdklab
2023-10-26 12:01 dpdklab
2023-10-26 12:01 dpdklab
2023-10-26 12:01 dpdklab
2023-10-26 12:01 dpdklab
2023-10-26 12:01 dpdklab
2023-10-26 12:01 dpdklab
2023-10-26 12:01 dpdklab
2023-10-26 12:01 dpdklab
2023-10-26 12:00 dpdklab
2023-10-26 12:00 dpdklab
2023-10-26 12:00 dpdklab
2023-10-26 12:00 dpdklab
2023-10-26 12:00 dpdklab
2023-10-26 12:00 dpdklab
2023-10-26 12:00 dpdklab
2023-10-26 12:00 dpdklab
2023-10-26 11:59 dpdklab
2023-10-26 11:59 dpdklab
2023-10-26 11:59 dpdklab
2023-10-26 11:59 dpdklab
2023-10-26 11:59 dpdklab
2023-10-26 11:58 dpdklab
2023-10-26 11:58 dpdklab
2023-10-26 11:58 dpdklab
2023-10-26 11:58 dpdklab
2023-10-26 11:58 dpdklab
2023-10-26 11:58 dpdklab
2023-10-26 11:57 dpdklab
2023-10-26 11:57 dpdklab
2023-10-26 11:57 dpdklab
2023-10-26 11:57 dpdklab
2023-10-26 11:57 dpdklab
2023-10-26 11:56 dpdklab
2023-10-26 11:55 dpdklab
2023-10-26 11:54 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=653a56e2.050a0220.62815.6cdfSMTPIN_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).