From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw134701 [PATCH] [v2] examples/ptp: replace terms master a
Date: Thu, 30 Nov 2023 19:06:18 -0800 (PST) [thread overview]
Message-ID: <65694daa.170a0220.f99b7.35b6SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/134701
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, November 29 2023 16:43:54
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:eeb0605f118dae66e80faa44f7b3e88748032353
134701 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28494/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-12-01 3:06 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 3:06 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-01 11:51 dpdklab
2023-12-01 10:35 dpdklab
2023-12-01 7:28 dpdklab
2023-12-01 7:15 dpdklab
2023-12-01 5:47 dpdklab
2023-12-01 5:26 dpdklab
2023-12-01 5:05 dpdklab
2023-12-01 5:04 dpdklab
2023-12-01 5:03 dpdklab
2023-12-01 4:58 dpdklab
2023-12-01 4:58 dpdklab
2023-12-01 4:57 dpdklab
2023-12-01 4:57 dpdklab
2023-12-01 4:52 dpdklab
2023-12-01 4:52 dpdklab
2023-12-01 4:49 dpdklab
2023-12-01 4:46 dpdklab
2023-12-01 4:46 dpdklab
2023-12-01 4:46 dpdklab
2023-12-01 4:46 dpdklab
2023-12-01 4:44 dpdklab
2023-12-01 4:44 dpdklab
2023-12-01 4:42 dpdklab
2023-12-01 4:41 dpdklab
2023-12-01 4:40 dpdklab
2023-12-01 4:39 dpdklab
2023-12-01 4:39 dpdklab
2023-12-01 4:37 dpdklab
2023-12-01 4:37 dpdklab
2023-12-01 4:37 dpdklab
2023-12-01 4:36 dpdklab
2023-12-01 4:36 dpdklab
2023-12-01 4:34 dpdklab
2023-12-01 4:34 dpdklab
2023-12-01 4:33 dpdklab
2023-12-01 4:29 dpdklab
2023-12-01 4:28 dpdklab
2023-12-01 4:28 dpdklab
2023-12-01 4:27 dpdklab
2023-12-01 4:26 dpdklab
2023-12-01 4:26 dpdklab
2023-12-01 4:26 dpdklab
2023-12-01 4:25 dpdklab
2023-12-01 4:24 dpdklab
2023-12-01 4:24 dpdklab
2023-12-01 4:23 dpdklab
2023-12-01 4:22 dpdklab
2023-12-01 3:52 dpdklab
2023-12-01 3:38 dpdklab
2023-12-01 3:38 dpdklab
2023-12-01 3:23 dpdklab
2023-12-01 3:04 dpdklab
2023-12-01 3:04 dpdklab
2023-12-01 3:03 dpdklab
2023-12-01 3:01 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=65694daa.170a0220.f99b7.35b6SMTPIN_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).