From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw147404 [PATCH] net/mlx5/hws: fix range definer error rec
Date: Sun, 27 Oct 2024 09:10:37 -0700 (PDT) [thread overview]
Message-ID: <671e65fd.250a0220.156b49.0a92SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241027130724.118001-1-getelson@nvidia.com>
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/147404
_Testing PASS_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Sunday, October 27 2024 13:07:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b57ec137a0c7fe126fde3b35793b454fb3272d48
147404 --> testing pass
Upstream job id: Aarch32-Unit-Test#4025
Test environment and result as below:
+-----------------------------+----------------+
| Environment | dpdk_unit_test |
+=============================+================+
| 32-bit Ubuntu 22.04.4 (ARM) | PASS |
+-----------------------------+----------------+
32-bit Ubuntu 22.04.4 (ARM)
Kernel: 5.15.83+ aarch64
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31701/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2024-10-27 16:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241027130724.118001-1-getelson@nvidia.com>
2024-10-27 12:37 ` |SUCCESS| pw147404 [PATCH] net/mlx5/hws: fix range definer error recovery qemudev
2024-10-27 12:41 ` qemudev
2024-10-27 13:08 ` checkpatch
2024-10-27 14:06 ` 0-day Robot
2024-10-27 15:01 ` |PENDING| pw147404 [PATCH] net/mlx5/hws: fix range definer error rec dpdklab
2024-10-27 15:07 ` |SUCCESS| " dpdklab
2024-10-27 15:11 ` dpdklab
2024-10-27 15:41 ` dpdklab
2024-10-27 15:45 ` dpdklab
2024-10-27 15:45 ` dpdklab
2024-10-27 15:51 ` dpdklab
2024-10-27 15:57 ` dpdklab
2024-10-27 16:10 ` dpdklab [this message]
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=671e65fd.250a0220.156b49.0a92SMTPIN_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).