From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw128741 [PATCH] [v1,1/1] maintainers: update maintainersh
Date: Thu, 15 Jun 2023 14:19:30 -0700 (PDT) [thread overview]
Message-ID: <648b8062.0d0a0220.2b7f7.6175SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-x86_64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/128741
_Testing PASS_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Thursday, June 15 2023 09:16:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:050de60d8a5cef8b7c10b4471905ca8bf69d670e
128741 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26704/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-15 21:19 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 21:19 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-17 13:02 dpdklab
2023-06-17 11:36 dpdklab
2023-06-16 8:57 dpdklab
2023-06-16 8:47 dpdklab
2023-06-16 8:43 dpdklab
2023-06-16 8:27 dpdklab
2023-06-16 8:22 dpdklab
2023-06-16 8:18 dpdklab
2023-06-16 8:13 dpdklab
2023-06-16 8:08 dpdklab
2023-06-16 7:52 dpdklab
2023-06-16 7:42 dpdklab
2023-06-15 21:47 dpdklab
2023-06-15 21:47 dpdklab
2023-06-15 21:18 dpdklab
2023-06-15 17:46 dpdklab
2023-06-15 17:37 dpdklab
2023-06-15 17:16 dpdklab
2023-06-15 16:57 dpdklab
2023-06-15 16:01 dpdklab
2023-06-15 14:53 dpdklab
2023-06-15 12:15 dpdklab
2023-06-15 12:14 dpdklab
2023-06-15 12:07 dpdklab
2023-06-15 12:02 dpdklab
2023-06-15 12:02 dpdklab
2023-06-15 11:52 dpdklab
2023-06-15 11:51 dpdklab
2023-06-15 11:46 dpdklab
2023-06-15 11:46 dpdklab
2023-06-15 11:45 dpdklab
2023-06-15 11:45 dpdklab
2023-06-15 11:44 dpdklab
2023-06-15 11:40 dpdklab
2023-06-15 11:35 dpdklab
2023-06-15 11:35 dpdklab
2023-06-15 11:35 dpdklab
2023-06-15 11:34 dpdklab
2023-06-15 11:31 dpdklab
2023-06-15 11:23 dpdklab
2023-06-15 11:21 dpdklab
2023-06-15 11:17 dpdklab
2023-06-15 11:13 dpdklab
2023-06-15 11:12 dpdklab
2023-06-15 11:09 dpdklab
2023-06-15 11:07 dpdklab
2023-06-15 11:04 dpdklab
2023-06-15 10:59 dpdklab
2023-06-15 10:57 dpdklab
2023-06-15 10:57 dpdklab
2023-06-15 10:50 dpdklab
2023-06-15 10:15 dpdklab
2023-06-15 10:09 dpdklab
2023-06-15 10:08 dpdklab
2023-06-15 10:08 dpdklab
2023-06-15 10:03 dpdklab
2023-06-15 10:02 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=648b8062.0d0a0220.2b7f7.6175SMTPIN_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).