From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132285 [PATCH] eventdev: drop custom OS defines
Date: Tue, 03 Oct 2023 10:43:33 -0700 (PDT) [thread overview]
Message-ID: <651c52c5.170a0220.7e94f.444aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132285
_Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Tuesday, October 03 2023 17:01:15
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: master
CommitID:9b1122634e8affeb1a3d957f3a96e48ae17956bc
132285 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27815/
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-03 17:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 17:43 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-03 19:50 dpdklab
2023-10-03 19:12 dpdklab
2023-10-03 18:59 dpdklab
2023-10-03 18:55 dpdklab
2023-10-03 18:51 dpdklab
2023-10-03 18:49 dpdklab
2023-10-03 18:38 dpdklab
2023-10-03 18:16 dpdklab
2023-10-03 17:58 dpdklab
2023-10-03 17:57 dpdklab
2023-10-03 17:56 dpdklab
2023-10-03 17:55 dpdklab
2023-10-03 17:55 dpdklab
2023-10-03 17:55 dpdklab
2023-10-03 17:55 dpdklab
2023-10-03 17:55 dpdklab
2023-10-03 17:48 dpdklab
2023-10-03 17:48 dpdklab
2023-10-03 17:48 dpdklab
2023-10-03 17:47 dpdklab
2023-10-03 17:47 dpdklab
2023-10-03 17:44 dpdklab
2023-10-03 17:43 dpdklab
2023-10-03 17:43 dpdklab
2023-10-03 17:40 dpdklab
2023-10-03 17:39 dpdklab
2023-10-03 17:38 dpdklab
2023-10-03 17:38 dpdklab
2023-10-03 17:37 dpdklab
2023-10-03 17:37 dpdklab
2023-10-03 17:36 dpdklab
2023-10-03 17:35 dpdklab
2023-10-03 17:35 dpdklab
2023-10-03 17:34 dpdklab
2023-10-03 17:34 dpdklab
2023-10-03 17:33 dpdklab
2023-10-03 17:33 dpdklab
[not found] <20231003170115.571133-1-bruce.richardson@intel.com>
2023-10-03 16:42 ` qemudev
2023-10-03 17:03 ` checkpatch
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=651c52c5.170a0220.7e94f.444aSMTPIN_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).