From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135250-135262 [PATCH] [v3,14/14] lib: use per line loggi
Date: Mon, 18 Dec 2023 02:59:19 -0800 (PST) [thread overview]
Message-ID: <65802607.050a0220.4b672.d340SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135262
_Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Monday, December 18 2023 09:27:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135250-135262 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28657/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-18 10:59 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 10:59 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-18 13:51 dpdklab
2023-12-18 13:42 dpdklab
2023-12-18 13:28 dpdklab
2023-12-18 12:04 dpdklab
2023-12-18 11:59 dpdklab
2023-12-18 11:42 dpdklab
2023-12-18 11:32 dpdklab
2023-12-18 11:27 dpdklab
2023-12-18 11:20 dpdklab
2023-12-18 11:20 dpdklab
2023-12-18 11:15 dpdklab
2023-12-18 11:14 dpdklab
2023-12-18 11:11 dpdklab
2023-12-18 11:09 dpdklab
2023-12-18 11:08 dpdklab
2023-12-18 11:04 dpdklab
2023-12-18 11:03 dpdklab
2023-12-18 10:58 dpdklab
2023-12-18 10:57 dpdklab
2023-12-18 10:56 dpdklab
2023-12-18 10:55 dpdklab
2023-12-18 10:54 dpdklab
2023-12-18 10:54 dpdklab
2023-12-18 10:53 dpdklab
2023-12-18 10:53 dpdklab
2023-12-18 10:51 dpdklab
2023-12-18 10:50 dpdklab
2023-12-18 10:50 dpdklab
2023-12-18 10:49 dpdklab
2023-12-18 10:48 dpdklab
2023-12-18 10:47 dpdklab
2023-12-18 10:45 dpdklab
2023-12-18 10:44 dpdklab
2023-12-18 10:42 dpdklab
2023-12-18 10:37 dpdklab
2023-12-18 10:37 dpdklab
2023-12-18 10:36 dpdklab
2023-12-18 10:35 dpdklab
2023-12-18 10:30 dpdklab
2023-12-18 10:28 dpdklab
2023-12-18 10:28 dpdklab
2023-12-18 10:28 dpdklab
2023-12-18 10:26 dpdklab
2023-12-18 10:26 dpdklab
2023-12-18 10:25 dpdklab
2023-12-18 10:25 dpdklab
2023-12-18 10:25 dpdklab
2023-12-18 10:24 dpdklab
2023-12-18 10:23 dpdklab
2023-12-18 10:23 dpdklab
2023-12-18 10:22 dpdklab
2023-12-18 10:22 dpdklab
2023-12-18 10:21 dpdklab
2023-12-18 10:20 dpdklab
2023-12-18 10:18 dpdklab
2023-12-18 10:17 dpdklab
2023-12-18 10:17 dpdklab
2023-12-18 10:13 dpdklab
2023-12-18 10:12 dpdklab
2023-12-18 10:08 dpdklab
2023-12-18 10:07 dpdklab
2023-12-18 10:07 dpdklab
2023-12-18 10:07 dpdklab
2023-12-18 10:04 dpdklab
2023-12-18 10:04 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=65802607.050a0220.4b672.d340SMTPIN_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).