From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135042-135044 [PATCH] [3/3] examples/vm_power_manager: d
Date: Mon, 11 Dec 2023 14:56:16 -0800 (PST) [thread overview]
Message-ID: <65779390.050a0220.18586.9eeaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/135044
_Functional Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Monday, December 11 2023 17:23:25
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:f2d5afbb2c05d7647da7ea914887c52115652651
135042-135044 --> 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
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/28588/
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-11 22:56 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 22:56 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-12-12 4:48 dpdklab
2023-12-12 1:39 dpdklab
2023-12-12 0:00 dpdklab
2023-12-11 23:49 dpdklab
2023-12-11 23:49 dpdklab
2023-12-11 23:48 dpdklab
2023-12-11 23:47 dpdklab
2023-12-11 23:34 dpdklab
2023-12-11 23:33 dpdklab
2023-12-11 23:32 dpdklab
2023-12-11 23:32 dpdklab
2023-12-11 23:31 dpdklab
2023-12-11 23:30 dpdklab
2023-12-11 23:30 dpdklab
2023-12-11 23:26 dpdklab
2023-12-11 23:26 dpdklab
2023-12-11 23:26 dpdklab
2023-12-11 23:25 dpdklab
2023-12-11 23:25 dpdklab
2023-12-11 23:25 dpdklab
2023-12-11 23:25 dpdklab
2023-12-11 23:25 dpdklab
2023-12-11 23:25 dpdklab
2023-12-11 23:25 dpdklab
2023-12-11 23:25 dpdklab
2023-12-11 23:25 dpdklab
2023-12-11 23:25 dpdklab
2023-12-11 23:25 dpdklab
2023-12-11 23:17 dpdklab
2023-12-11 23:16 dpdklab
2023-12-11 23:15 dpdklab
2023-12-11 23:15 dpdklab
2023-12-11 23:14 dpdklab
2023-12-11 23:13 dpdklab
2023-12-11 23:12 dpdklab
2023-12-11 23:11 dpdklab
2023-12-11 23:10 dpdklab
2023-12-11 23:08 dpdklab
2023-12-11 23:08 dpdklab
2023-12-11 23:07 dpdklab
2023-12-11 23:06 dpdklab
2023-12-11 23:03 dpdklab
2023-12-11 22:59 dpdklab
2023-12-11 22:58 dpdklab
2023-12-11 22:26 dpdklab
2023-12-11 22:24 dpdklab
2023-12-11 22:18 dpdklab
2023-12-11 22:18 dpdklab
2023-12-11 22:17 dpdklab
2023-12-11 22:17 dpdklab
2023-12-11 22:09 dpdklab
2023-12-11 22:07 dpdklab
2023-12-11 22:01 dpdklab
2023-12-11 21:57 dpdklab
2023-12-11 21:56 dpdklab
2023-12-11 21:55 dpdklab
2023-12-11 21:55 dpdklab
2023-12-11 21:53 dpdklab
2023-12-11 21:53 dpdklab
2023-12-11 21:52 dpdklab
2023-12-11 21:51 dpdklab
2023-12-11 21:49 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=65779390.050a0220.18586.9eeaSMTPIN_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).