From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132307 [PATCH] [v2] eventdev: drop custom OS defines
Date: Wed, 04 Oct 2023 10:24:09 -0700 (PDT) [thread overview]
Message-ID: <651d9fb9.0c0a0220.3f127.6b0bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132307
_Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Wednesday, October 04 2023 16:28:34
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:687a5b12b14f02f0d3624f4b36b34dba8119a680
132307 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27827/
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-04 17:24 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 17:24 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-04 18:58 dpdklab
2023-10-04 18:12 dpdklab
2023-10-04 18:05 dpdklab
2023-10-04 18:05 dpdklab
2023-10-04 18:04 dpdklab
2023-10-04 18:03 dpdklab
2023-10-04 17:59 dpdklab
2023-10-04 17:54 dpdklab
2023-10-04 17:53 dpdklab
2023-10-04 17:53 dpdklab
2023-10-04 17:53 dpdklab
2023-10-04 17:30 dpdklab
[not found] <20231004162834.249828-1-bruce.richardson@intel.com>
2023-10-04 16:17 ` |SUCCESS| pw132307 [PATCH v2] " qemudev
2023-10-04 16:21 ` qemudev
2023-10-04 16:36 ` checkpatch
2023-10-04 17:27 ` 0-day Robot
2023-10-04 17:25 |SUCCESS| pw132307 [PATCH] [v2] " dpdklab
2023-10-04 17:24 dpdklab
2023-10-04 17:23 dpdklab
2023-10-04 17:23 dpdklab
2023-10-04 17:23 dpdklab
2023-10-04 17:23 dpdklab
2023-10-04 17:23 dpdklab
2023-10-04 17:23 dpdklab
2023-10-04 17:23 dpdklab
2023-10-04 17:23 dpdklab
2023-10-04 17:23 dpdklab
2023-10-04 17:22 dpdklab
2023-10-04 17:22 dpdklab
2023-10-04 17:22 dpdklab
2023-10-04 17:22 dpdklab
2023-10-04 17:21 dpdklab
2023-10-04 17:21 dpdklab
2023-10-04 17:21 dpdklab
2023-10-04 17:20 dpdklab
2023-10-04 17:18 dpdklab
2023-10-04 17:18 dpdklab
2023-10-04 17:18 dpdklab
2023-10-04 17:18 dpdklab
2023-10-04 17:18 dpdklab
2023-10-04 17:17 dpdklab
2023-10-04 17:17 dpdklab
2023-10-04 17:17 dpdklab
2023-10-04 17:17 dpdklab
2023-10-04 17:16 dpdklab
2023-10-04 17:14 dpdklab
2023-10-04 17:09 dpdklab
2023-10-04 17:08 dpdklab
2023-10-04 17:08 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=651d9fb9.0c0a0220.3f127.6b0bSMTPIN_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).