From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130612 [PATCH] [v3] common/mlx5: replace use of PMD logt
Date: Tue, 22 Aug 2023 16:53:24 -0700 (PDT) [thread overview]
Message-ID: <64e54a74.050a0220.2725e.61a1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130612
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Monday, August 21 2023 16:16:25
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:971d2b57972919527e27ed683032a71864a2eb56
130612 --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| CentOS Stream 8 | PASS |
+------------------+----------------+
| CentOS Stream 9 | PASS |
+------------------+----------------+
| Debian Bullseye | PASS |
+------------------+----------------+
| Debian Buster | PASS |
+------------------+----------------+
| Fedora 37 | PASS |
+------------------+----------------+
| Fedora 38 | PASS |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
| Ubuntu 20.04 | PASS |
+------------------+----------------+
| RHEL8 | 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
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 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.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)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27404/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-22 23:53 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 23:53 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-23 13:45 dpdklab
2023-08-23 13:28 dpdklab
2023-08-23 13:23 dpdklab
2023-08-23 13:17 dpdklab
2023-08-23 13:13 dpdklab
2023-08-23 5:50 dpdklab
2023-08-23 3:11 dpdklab
2023-08-23 0:45 dpdklab
2023-08-23 0:10 dpdklab
2023-08-23 0:09 dpdklab
2023-08-23 0:08 dpdklab
2023-08-23 0:07 dpdklab
2023-08-23 0:06 dpdklab
2023-08-23 0:06 dpdklab
2023-08-23 0:06 dpdklab
2023-08-23 0:05 dpdklab
2023-08-22 23:57 dpdklab
2023-08-22 23:55 dpdklab
2023-08-22 23:54 dpdklab
2023-08-22 23:54 dpdklab
2023-08-22 23:53 dpdklab
2023-08-22 23:53 dpdklab
2023-08-22 23:52 dpdklab
2023-08-22 23:52 dpdklab
2023-08-22 23:52 dpdklab
2023-08-22 23:51 dpdklab
2023-08-22 23:47 dpdklab
2023-08-22 23:45 dpdklab
2023-08-22 23:44 dpdklab
2023-08-22 23:43 dpdklab
2023-08-22 23:34 dpdklab
2023-08-22 23:33 dpdklab
2023-08-22 23:33 dpdklab
2023-08-22 23:33 dpdklab
2023-08-22 23:32 dpdklab
2023-08-22 23:31 dpdklab
2023-08-22 23:23 dpdklab
2023-08-22 23:20 dpdklab
2023-08-22 23:19 dpdklab
2023-08-22 23:19 dpdklab
2023-08-22 23:19 dpdklab
2023-08-22 23:19 dpdklab
2023-08-22 23:19 dpdklab
2023-08-22 23:19 dpdklab
2023-08-22 23:19 dpdklab
2023-08-22 23:19 dpdklab
2023-08-22 23:19 dpdklab
2023-08-22 23:18 dpdklab
2023-08-22 23:18 dpdklab
2023-08-22 23:18 dpdklab
2023-08-22 23:17 dpdklab
2023-08-22 23:16 dpdklab
2023-08-22 23:15 dpdklab
2023-08-22 23:12 dpdklab
2023-08-22 21:57 dpdklab
2023-08-22 21:53 dpdklab
2023-08-22 21:51 dpdklab
2023-08-22 21:47 dpdklab
2023-08-22 21:15 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=64e54a74.050a0220.2725e.61a1SMTPIN_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).