From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136653-136673 [PATCH] [v2,21/21] devtools: forbid direct
Date: Tue, 13 Feb 2024 16:21:50 -0800 (PST) [thread overview]
Message-ID: <65cc079e.050a0220.bf07f.a0bbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/136673
_Functional Testing PASS_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tuesday, February 13 2024 18:34:52
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:31d72ff4dc7c057366153e9918ac92bf9123a3bc
136653-136673 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.82
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/29139/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-14 0:21 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-14 0:21 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-14 6:27 dpdklab
2024-02-14 4:26 dpdklab
2024-02-14 3:37 dpdklab
2024-02-14 3:31 dpdklab
2024-02-14 3:27 dpdklab
2024-02-14 3:23 dpdklab
2024-02-14 3:23 dpdklab
2024-02-14 3:21 dpdklab
2024-02-14 3:19 dpdklab
2024-02-14 3:17 dpdklab
2024-02-14 3:07 dpdklab
2024-02-14 3:07 dpdklab
2024-02-14 3:06 dpdklab
2024-02-14 3:00 dpdklab
2024-02-14 2:58 dpdklab
2024-02-14 2:58 dpdklab
2024-02-14 2:58 dpdklab
2024-02-14 2:55 dpdklab
2024-02-14 2:47 dpdklab
2024-02-14 2:47 dpdklab
2024-02-14 2:45 dpdklab
2024-02-14 2:35 dpdklab
2024-02-14 2:32 dpdklab
2024-02-14 2:32 dpdklab
2024-02-14 2:31 dpdklab
2024-02-14 2:27 dpdklab
2024-02-14 1:59 dpdklab
2024-02-14 1:58 dpdklab
2024-02-14 1:58 dpdklab
2024-02-14 1:57 dpdklab
2024-02-14 1:51 dpdklab
2024-02-14 1:22 dpdklab
2024-02-14 1:01 dpdklab
2024-02-14 0:59 dpdklab
2024-02-14 0:58 dpdklab
2024-02-14 0:52 dpdklab
2024-02-14 0:52 dpdklab
2024-02-14 0:51 dpdklab
2024-02-14 0:50 dpdklab
2024-02-14 0:50 dpdklab
2024-02-14 0:49 dpdklab
2024-02-14 0:49 dpdklab
2024-02-14 0:49 dpdklab
2024-02-14 0:46 dpdklab
2024-02-14 0:46 dpdklab
2024-02-14 0:39 dpdklab
2024-02-14 0:37 dpdklab
2024-02-14 0:30 dpdklab
2024-02-14 0:27 dpdklab
2024-02-14 0:24 dpdklab
2024-02-14 0:19 dpdklab
2024-02-14 0:19 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=65cc079e.050a0220.bf07f.a0bbSMTPIN_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).