From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Andrew Boyer <Andrew.Boyer@amd.com>
Subject: |SUCCESS| pw136340-136352 [PATCH] [13/13] net/ionic: optimize device
Date: Fri, 02 Feb 2024 12:30:18 -0800 (PST) [thread overview]
Message-ID: <65bd50da.170a0220.17b8c.21a8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136352
_Testing PASS_
Submitter: Andrew Boyer <Andrew.Boyer@amd.com>
Date: Friday, February 02 2024 19:32:38
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f8ecc0053ca52cb2310a9e1834ea583167a793cd
136340-136352 --> 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/29044/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-02 20:30 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 20:30 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-05 23:24 dpdklab
2024-02-05 22:50 dpdklab
2024-02-05 21:18 dpdklab
2024-02-05 20:59 dpdklab
2024-02-05 20:32 dpdklab
2024-02-05 20:24 dpdklab
2024-02-05 20:16 dpdklab
2024-02-05 20:09 dpdklab
2024-02-05 20:05 dpdklab
2024-02-05 19:57 dpdklab
2024-02-05 19:53 dpdklab
2024-02-03 1:17 dpdklab
2024-02-03 0:42 dpdklab
2024-02-02 21:56 dpdklab
2024-02-02 21:28 dpdklab
2024-02-02 21:04 dpdklab
2024-02-02 20:56 dpdklab
2024-02-02 20:52 dpdklab
2024-02-02 20:49 dpdklab
2024-02-02 20:49 dpdklab
2024-02-02 20:46 dpdklab
2024-02-02 20:45 dpdklab
2024-02-02 20:43 dpdklab
2024-02-02 20:43 dpdklab
2024-02-02 20:41 dpdklab
2024-02-02 20:41 dpdklab
2024-02-02 20:40 dpdklab
2024-02-02 20:40 dpdklab
2024-02-02 20:39 dpdklab
2024-02-02 20:39 dpdklab
2024-02-02 20:39 dpdklab
2024-02-02 20:38 dpdklab
2024-02-02 20:38 dpdklab
2024-02-02 20:36 dpdklab
2024-02-02 20:36 dpdklab
2024-02-02 20:34 dpdklab
2024-02-02 20:29 dpdklab
2024-02-02 20:27 dpdklab
2024-02-02 20:26 dpdklab
2024-02-02 20:25 dpdklab
2024-02-02 20:25 dpdklab
2024-02-02 20:24 dpdklab
2024-02-02 20:24 dpdklab
2024-02-02 20:23 dpdklab
2024-02-02 20:22 dpdklab
2024-02-02 20:22 dpdklab
2024-02-02 20:22 dpdklab
2024-02-02 20:22 dpdklab
2024-02-02 20:21 dpdklab
2024-02-02 20:21 dpdklab
2024-02-02 20:20 dpdklab
2024-02-02 20:19 dpdklab
2024-02-02 20:18 dpdklab
2024-02-02 20:18 dpdklab
2024-02-02 20:17 dpdklab
2024-02-02 20:17 dpdklab
2024-02-02 20:17 dpdklab
2024-02-02 20:16 dpdklab
2024-02-02 20:14 dpdklab
2024-02-02 20:14 dpdklab
2024-02-02 20:13 dpdklab
2024-02-02 20:13 dpdklab
2024-02-02 20:13 dpdklab
2024-02-02 20:12 dpdklab
2024-02-02 20:12 dpdklab
2024-02-02 20:11 dpdklab
2024-02-02 20:11 dpdklab
2024-02-02 20:11 dpdklab
2024-02-02 20:11 dpdklab
2024-02-02 20:10 dpdklab
2024-02-02 20:10 dpdklab
2024-02-02 20:10 dpdklab
2024-02-02 20:10 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=65bd50da.170a0220.17b8c.21a8SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=Andrew.Boyer@amd.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).