From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: |SUCCESS| pw132144-132145 [PATCH] [2/2] event/*: add driver selftest
Date: Thu, 28 Sep 2023 12:07:13 -0700 (PDT) [thread overview]
Message-ID: <6515cee1.0d0a0220.e9e6.ab89SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132145
_Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Thursday, September 28 2023 15:14:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c56185fc183fc0532d2f03aaf04bbf0989ea91a5
132144-132145 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27777/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-28 19:07 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 19:07 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-28 23:00 dpdklab
2023-09-28 19:53 dpdklab
2023-09-28 19:46 dpdklab
2023-09-28 19:41 dpdklab
2023-09-28 19:38 dpdklab
2023-09-28 19:34 dpdklab
2023-09-28 19:29 dpdklab
2023-09-28 19:25 dpdklab
2023-09-28 19:20 dpdklab
2023-09-28 19:19 dpdklab
2023-09-28 19:16 dpdklab
2023-09-28 19:13 dpdklab
2023-09-28 18:23 dpdklab
2023-09-28 17:18 dpdklab
2023-09-28 17:16 dpdklab
2023-09-28 17:14 dpdklab
2023-09-28 17:14 dpdklab
2023-09-28 17:13 dpdklab
2023-09-28 17:12 dpdklab
2023-09-28 17:12 dpdklab
2023-09-28 17:12 dpdklab
2023-09-28 17:10 dpdklab
2023-09-28 17:10 dpdklab
2023-09-28 17:09 dpdklab
2023-09-28 17:09 dpdklab
2023-09-28 17:09 dpdklab
2023-09-28 17:03 dpdklab
2023-09-28 16:53 dpdklab
2023-09-28 16:48 dpdklab
2023-09-28 16:47 dpdklab
2023-09-28 16:47 dpdklab
2023-09-28 16:45 dpdklab
2023-09-28 16:44 dpdklab
2023-09-28 16:43 dpdklab
2023-09-28 16:43 dpdklab
2023-09-28 16:42 dpdklab
2023-09-28 16:41 dpdklab
2023-09-28 16:40 dpdklab
2023-09-28 16:39 dpdklab
2023-09-28 16:39 dpdklab
2023-09-28 16:38 dpdklab
2023-09-28 16:38 dpdklab
2023-09-28 16:37 dpdklab
2023-09-28 16:37 dpdklab
2023-09-28 16:34 dpdklab
2023-09-28 16:28 dpdklab
2023-09-28 16:26 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=6515cee1.0d0a0220.e9e6.ab89SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=bruce.richardson@intel.com \
--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).