From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129529-129530 [PATCH] [v6,2/2] dts: add paramiko to depe
Date: Thu, 13 Jul 2023 10:13:25 -0700 (PDT) [thread overview]
Message-ID: <64b030b5.810a0220.65d53.af8fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/129530
_Functional Testing PASS_
Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Thursday, July 13 2023 15:21:06
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:655eb37b18b1b0dc4d106acdf0dfedde01cfb224
129529-129530 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27068/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-13 17:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 17:13 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-14 18:35 dpdklab
2023-07-14 18:30 dpdklab
2023-07-14 18:26 dpdklab
2023-07-14 18:10 dpdklab
2023-07-14 17:59 dpdklab
2023-07-14 3:43 dpdklab
2023-07-14 3:43 dpdklab
2023-07-13 20:42 dpdklab
2023-07-13 20:33 dpdklab
2023-07-13 20:20 dpdklab
2023-07-13 19:31 dpdklab
2023-07-13 18:36 dpdklab
2023-07-13 17:46 dpdklab
2023-07-13 17:40 dpdklab
2023-07-13 17:28 dpdklab
2023-07-13 17:25 dpdklab
2023-07-13 17:23 dpdklab
2023-07-13 17:23 dpdklab
2023-07-13 17:22 dpdklab
2023-07-13 17:21 dpdklab
2023-07-13 17:18 dpdklab
2023-07-13 17:18 dpdklab
2023-07-13 17:13 dpdklab
2023-07-13 17:07 dpdklab
2023-07-13 17:05 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=64b030b5.810a0220.65d53.af8fSMTPIN_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).