From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133630 [PATCH] net/mlx5: reuse reformat and modify heade
Date: Mon, 30 Oct 2023 12:13:41 -0700 (PDT) [thread overview]
Message-ID: <65400065.050a0220.407c2.dbb6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133630
_Testing PASS_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Monday, October 30 2023 17:43:20
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: master
CommitID:6b6fa376a7d347086666527010fc8c559540f14a
133630 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-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
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28146/
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-30 19:13 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 19:13 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-31 0:32 dpdklab
2023-10-30 21:03 dpdklab
2023-10-30 19:17 dpdklab
2023-10-30 19:16 dpdklab
2023-10-30 19:14 dpdklab
2023-10-30 19:05 dpdklab
2023-10-30 19:03 dpdklab
2023-10-30 18:59 dpdklab
2023-10-30 18:57 dpdklab
2023-10-30 18:55 dpdklab
2023-10-30 18:53 dpdklab
2023-10-30 18:52 dpdklab
2023-10-30 18:47 dpdklab
2023-10-30 18:44 dpdklab
2023-10-30 18:43 dpdklab
2023-10-30 18:41 dpdklab
2023-10-30 18:40 dpdklab
2023-10-30 18:40 dpdklab
2023-10-30 18:39 dpdklab
2023-10-30 18:37 dpdklab
2023-10-30 18:37 dpdklab
2023-10-30 18:37 dpdklab
2023-10-30 18:36 dpdklab
2023-10-30 18:36 dpdklab
2023-10-30 18:35 dpdklab
2023-10-30 18:35 dpdklab
2023-10-30 18:35 dpdklab
2023-10-30 18:34 dpdklab
2023-10-30 18:34 dpdklab
2023-10-30 18:34 dpdklab
2023-10-30 18:34 dpdklab
2023-10-30 18:33 dpdklab
2023-10-30 18:33 dpdklab
2023-10-30 18:33 dpdklab
2023-10-30 18:33 dpdklab
2023-10-30 18:32 dpdklab
2023-10-30 18:31 dpdklab
2023-10-30 18:30 dpdklab
2023-10-30 18:29 dpdklab
2023-10-30 18:28 dpdklab
2023-10-30 18:27 dpdklab
2023-10-30 18:27 dpdklab
2023-10-30 18:26 dpdklab
2023-10-30 18:26 dpdklab
2023-10-30 18:26 dpdklab
2023-10-30 18:25 dpdklab
2023-10-30 18:25 dpdklab
2023-10-30 18:24 dpdklab
2023-10-30 18:24 dpdklab
2023-10-30 18:24 dpdklab
2023-10-30 18:23 dpdklab
2023-10-30 18:23 dpdklab
2023-10-30 18:23 dpdklab
2023-10-30 18:22 dpdklab
2023-10-30 18:22 dpdklab
2023-10-30 18:21 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=65400065.050a0220.407c2.dbb6SMTPIN_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).