From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129737-129739 [PATCH] [v6,3/3] telemetry: use standard l
Date: Mon, 31 Jul 2023 17:14:44 -0700 (PDT) [thread overview]
Message-ID: <64c84e74.810a0220.cfcf8.482bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-x86_64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129739
_Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Monday, July 31 2023 10:17:03
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:12fcafcd62286933e6b167b14856d21f642efa5f
129737-129739 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
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/27163/
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-01 0:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 0:14 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-01 0:14 dpdklab
2023-07-31 17:44 dpdklab
2023-07-31 17:34 dpdklab
2023-07-31 17:32 dpdklab
2023-07-31 17:30 dpdklab
2023-07-31 17:06 dpdklab
2023-07-31 17:03 dpdklab
2023-07-31 16:57 dpdklab
2023-07-31 15:01 dpdklab
2023-07-31 13:55 dpdklab
2023-07-31 13:46 dpdklab
2023-07-31 13:37 dpdklab
2023-07-31 13:25 dpdklab
2023-07-31 13:24 dpdklab
2023-07-31 13:16 dpdklab
2023-07-31 13:14 dpdklab
2023-07-31 13:12 dpdklab
2023-07-31 13:11 dpdklab
2023-07-31 13:09 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=64c84e74.810a0220.cfcf8.482bSMTPIN_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).