From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw130483 [PATCH] test: remove use of word master in test_r
Date: Thu, 17 Aug 2023 20:15:04 -0700 (PDT) [thread overview]
Message-ID: <64dee238.a70a0220.32ed5.2fe9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130483
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, August 18 2023 02:33:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:971d2b57972919527e27ed683032a71864a2eb56
130483 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
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/27374/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-18 3:15 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 3:15 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-18 20:11 dpdklab
2023-08-18 20:06 dpdklab
2023-08-18 19:56 dpdklab
2023-08-18 19:38 dpdklab
2023-08-18 19:33 dpdklab
2023-08-18 17:35 dpdklab
2023-08-18 15:35 dpdklab
2023-08-18 4:47 dpdklab
2023-08-18 4:40 dpdklab
2023-08-18 3:59 dpdklab
2023-08-18 3:42 dpdklab
2023-08-18 3:41 dpdklab
2023-08-18 3:38 dpdklab
2023-08-18 3:36 dpdklab
2023-08-18 3:35 dpdklab
2023-08-18 3:33 dpdklab
2023-08-18 3:32 dpdklab
2023-08-18 3:29 dpdklab
2023-08-18 3:29 dpdklab
2023-08-18 3:28 dpdklab
2023-08-18 3:27 dpdklab
2023-08-18 3:27 dpdklab
2023-08-18 3:26 dpdklab
2023-08-18 3:26 dpdklab
2023-08-18 3:26 dpdklab
2023-08-18 3:26 dpdklab
2023-08-18 3:26 dpdklab
2023-08-18 3:26 dpdklab
2023-08-18 3:26 dpdklab
2023-08-18 3:26 dpdklab
2023-08-18 3:25 dpdklab
2023-08-18 3:25 dpdklab
2023-08-18 3:25 dpdklab
2023-08-18 3:25 dpdklab
2023-08-18 3:24 dpdklab
2023-08-18 3:18 dpdklab
2023-08-18 3:18 dpdklab
2023-08-18 3:18 dpdklab
2023-08-18 3:18 dpdklab
2023-08-18 3:18 dpdklab
2023-08-18 3:18 dpdklab
2023-08-18 3:18 dpdklab
2023-08-18 3:17 dpdklab
2023-08-18 3:16 dpdklab
2023-08-18 3:16 dpdklab
2023-08-18 3:16 dpdklab
2023-08-18 3:15 dpdklab
2023-08-18 3:15 dpdklab
2023-08-18 3:14 dpdklab
2023-08-18 3:14 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=64dee238.a70a0220.32ed5.2fe9SMTPIN_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).