From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135903 [PATCH] [v3] event/dsw: optimize serving port log
Date: Wed, 17 Jan 2024 21:44:06 -0800 (PST) [thread overview]
Message-ID: <65a8baa6.810a0220.a5f09.4004SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135903
_Testing PASS_
Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Wednesday, January 17 2024 07:41:11
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a1dff49b89249659bb40512bb1410a9afba0f382
135903 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28881/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-18 5:44 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 5:44 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-18 14:24 dpdklab
2024-01-18 8:02 dpdklab
2024-01-18 7:52 dpdklab
2024-01-18 7:39 dpdklab
2024-01-18 7:37 dpdklab
2024-01-18 7:34 dpdklab
2024-01-18 6:52 dpdklab
2024-01-18 6:51 dpdklab
2024-01-18 6:49 dpdklab
2024-01-18 6:46 dpdklab
2024-01-18 6:41 dpdklab
2024-01-18 6:41 dpdklab
2024-01-18 6:33 dpdklab
2024-01-18 6:31 dpdklab
2024-01-18 6:28 dpdklab
2024-01-18 6:28 dpdklab
2024-01-18 6:25 dpdklab
2024-01-18 6:09 dpdklab
2024-01-18 6:07 dpdklab
2024-01-18 6:07 dpdklab
2024-01-18 6:06 dpdklab
2024-01-18 6:06 dpdklab
2024-01-18 6:06 dpdklab
2024-01-18 5:55 dpdklab
2024-01-18 5:54 dpdklab
2024-01-18 5:52 dpdklab
2024-01-18 5:52 dpdklab
2024-01-18 5:51 dpdklab
2024-01-18 5:50 dpdklab
2024-01-18 5:48 dpdklab
2024-01-18 5:46 dpdklab
2024-01-18 5:46 dpdklab
2024-01-18 5:45 dpdklab
2024-01-18 5:45 dpdklab
2024-01-18 5:44 dpdklab
2024-01-18 5:44 dpdklab
2024-01-18 5:44 dpdklab
2024-01-18 5:43 dpdklab
2024-01-18 5:41 dpdklab
2024-01-18 5:39 dpdklab
2024-01-18 5:38 dpdklab
2024-01-18 5:33 dpdklab
2024-01-18 5:32 dpdklab
2024-01-18 5:24 dpdklab
2024-01-18 5:20 dpdklab
2024-01-18 5:16 dpdklab
2024-01-18 5:15 dpdklab
2024-01-18 5:15 dpdklab
2024-01-18 5:13 dpdklab
2024-01-18 5:08 dpdklab
2024-01-18 5:05 dpdklab
2024-01-18 4:54 dpdklab
2024-01-18 4:46 dpdklab
2024-01-18 4:43 dpdklab
2024-01-18 4:41 dpdklab
2024-01-18 4:36 dpdklab
2024-01-18 4:35 dpdklab
2024-01-18 4:35 dpdklab
2024-01-18 4:28 dpdklab
2024-01-18 4:21 dpdklab
2024-01-18 4:18 dpdklab
2024-01-18 4:14 dpdklab
2024-01-18 4:14 dpdklab
2024-01-18 4:11 dpdklab
2024-01-18 4:09 dpdklab
2024-01-18 3:54 dpdklab
2024-01-18 3:53 dpdklab
2024-01-18 3:52 dpdklab
2024-01-18 3:51 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=65a8baa6.810a0220.a5f09.4004SMTPIN_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).