From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139989-139990 [PATCH] [v6,2/2] dts: Change hugepage 'amo
Date: Tue, 07 May 2024 10:24:08 -0700 (PDT) [thread overview]
Message-ID: <663a63b8.170a0220.6a453.9b33SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240507163752.305-3-npratte@iol.unh.edu>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/139990
_Functional Testing PASS_
Submitter: Nicholas Pratte <npratte@iol.unh.edu>
Date: Tuesday, May 07 2024 16:37:52
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139989-139990 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29924/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-05-07 17:24 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240507163752.305-3-npratte@iol.unh.edu>
2024-05-07 16:13 ` |SUCCESS| pw139989-139990 [PATCH v6 2/2] dts: Change hugepage 'amount' to a different term qemudev
2024-05-07 16:17 ` qemudev
2024-05-07 16:39 ` |SUCCESS| pw139990 " checkpatch
2024-05-07 17:21 ` |SUCCESS| pw139989-139990 [PATCH] [v6,2/2] dts: Change hugepage 'amo dpdklab
2024-05-07 17:21 ` dpdklab
2024-05-07 17:22 ` dpdklab
2024-05-07 17:22 ` dpdklab
2024-05-07 17:23 ` dpdklab
2024-05-07 17:24 ` dpdklab [this message]
2024-05-07 17:28 ` dpdklab
2024-05-07 17:29 ` dpdklab
2024-05-07 17:29 ` dpdklab
2024-05-07 17:30 ` dpdklab
2024-05-07 17:30 ` dpdklab
2024-05-07 17:30 ` dpdklab
2024-05-07 17:31 ` dpdklab
2024-05-07 17:31 ` dpdklab
2024-05-07 17:31 ` dpdklab
2024-05-07 17:31 ` dpdklab
2024-05-07 17:31 ` dpdklab
2024-05-07 17:31 ` dpdklab
2024-05-07 17:32 ` dpdklab
2024-05-07 17:32 ` dpdklab
2024-05-07 17:32 ` dpdklab
2024-05-07 17:32 ` dpdklab
2024-05-07 17:32 ` dpdklab
2024-05-07 17:33 ` dpdklab
2024-05-07 17:33 ` dpdklab
2024-05-07 17:33 ` dpdklab
2024-05-07 17:33 ` dpdklab
2024-05-07 17:33 ` dpdklab
2024-05-07 17:33 ` dpdklab
2024-05-07 17:34 ` dpdklab
2024-05-07 17:34 ` dpdklab
2024-05-07 17:37 ` dpdklab
2024-05-07 17:37 ` dpdklab
2024-05-07 17:38 ` dpdklab
2024-05-07 17:39 ` dpdklab
2024-05-07 17:39 ` dpdklab
2024-05-07 17:39 ` dpdklab
2024-05-07 17:39 ` dpdklab
2024-05-07 17:40 ` dpdklab
2024-05-07 17:40 ` dpdklab
2024-05-07 17:40 ` dpdklab
2024-05-07 17:40 ` dpdklab
2024-05-07 17:40 ` dpdklab
2024-05-07 17:41 ` dpdklab
2024-05-07 17:41 ` dpdklab
2024-05-07 17:42 ` dpdklab
2024-05-07 17:42 ` dpdklab
2024-05-07 17:42 ` dpdklab
2024-05-07 17:43 ` dpdklab
2024-05-07 17:44 ` dpdklab
2024-05-07 17:44 ` dpdklab
2024-05-07 17:44 ` dpdklab
2024-05-07 17:45 ` dpdklab
2024-05-07 17:45 ` dpdklab
2024-05-07 17:46 ` dpdklab
2024-05-07 17:46 ` dpdklab
2024-05-07 17:46 ` dpdklab
2024-05-07 17:47 ` dpdklab
2024-05-07 17:47 ` dpdklab
2024-05-07 17:47 ` dpdklab
2024-05-07 17:52 ` dpdklab
2024-05-07 18:09 ` dpdklab
2024-05-07 18:09 ` dpdklab
2024-05-07 18:10 ` dpdklab
2024-05-07 18:10 ` dpdklab
2024-05-07 18:11 ` dpdklab
2024-05-07 18:11 ` dpdklab
2024-05-07 18:12 ` dpdklab
2024-05-07 18:12 ` dpdklab
2024-05-07 18:13 ` dpdklab
2024-05-07 18:13 ` dpdklab
2024-05-07 18:14 ` dpdklab
2024-05-07 18:14 ` dpdklab
2024-05-07 18:15 ` dpdklab
2024-05-07 18:16 ` dpdklab
2024-05-07 18:16 ` dpdklab
2024-05-07 18:16 ` dpdklab
2024-05-07 18:18 ` dpdklab
2024-05-07 18:20 ` dpdklab
2024-05-07 18:23 ` dpdklab
2024-05-07 18:24 ` dpdklab
2024-05-07 18:36 ` dpdklab
2024-05-07 18:44 ` dpdklab
2024-05-07 18:50 ` 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=663a63b8.170a0220.6a453.9b33SMTPIN_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).