From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw103025 [PATCH] [v7] doc: add metering limitation in mlx5 guide
Date: Fri, 29 Oct 2021 03:31:21 -0400 (EDT) [thread overview]
Message-ID: <20211029073121.A47D460524@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
Test-Label: iol-aarch64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/103025
_Testing PASS_
Submitter: Li Zhang <lizh@nvidia.com>
Date: Wednesday, October 27 2021 09:13:58
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b66412f24f17fcba5a248888bf4b3c1f5d6880de
103025 --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| Ubuntu 20.04 ARM | PASS |
+------------------+----------------+
Ubuntu 20.04 ARM
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/19766/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2021-10-29 7:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 7:31 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-28 15:07 dpdklab
2021-10-28 14:49 dpdklab
2021-10-28 5:38 dpdklab
2021-10-28 4:25 dpdklab
2021-10-28 4:12 dpdklab
2021-10-28 3:59 dpdklab
2021-10-27 13:26 dpdklab
2021-10-27 13:10 dpdklab
2021-10-27 12:17 dpdklab
2021-10-27 12:06 dpdklab
2021-10-27 12:02 dpdklab
2021-10-27 12:00 dpdklab
2021-10-27 12:00 dpdklab
2021-10-27 11:46 dpdklab
[not found] <20211027091359.165070-1-lizh@nvidia.com>
2021-10-27 9:15 ` [dpdk-test-report] |SUCCESS| pw103025 [PATCH v7] " checkpatch
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=20211029073121.A47D460524@noxus.dpdklab.iol.unh.edu \
--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).