From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143845-143840 [PATCH] [6/6] eal: keep per-lcore power in
Date: Wed, 11 Sep 2024 04:55:44 -0700 (PDT) [thread overview]
Message-ID: <66e18540.170a0220.31708f.17ddSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240910070344.699183-7-mattias.ronnblom@ericsson.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143840
_Functional Testing PASS_
Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Tuesday, September 10 2024 07:03:44
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
143845-143840 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#179793
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
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30981/
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-09-11 11:55 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240910070344.699183-7-mattias.ronnblom@ericsson.com>
2024-09-10 6:47 ` |SUCCESS| pw143845-143840 [PATCH 6/6] eal: keep per-lcore power intrinsics state in lcore variable qemudev
2024-09-10 6:52 ` qemudev
2024-09-10 7:14 ` |SUCCESS| pw143840 " checkpatch
2024-09-10 8:05 ` |FAILURE| " 0-day Robot
2024-09-11 0:18 ` |SUCCESS| pw143845-143840 [PATCH] [6/6] eal: keep per-lcore power in dpdklab
2024-09-11 0:49 ` dpdklab
2024-09-11 2:14 ` dpdklab
2024-09-11 3:02 ` |FAILURE| " dpdklab
2024-09-11 4:15 ` |WARNING| " dpdklab
2024-09-11 4:17 ` dpdklab
2024-09-11 4:18 ` dpdklab
2024-09-11 4:46 ` |PENDING| " dpdklab
2024-09-11 5:53 ` |FAILURE| " dpdklab
2024-09-11 5:54 ` dpdklab
2024-09-11 6:00 ` dpdklab
2024-09-11 6:00 ` dpdklab
2024-09-11 6:02 ` dpdklab
2024-09-11 6:05 ` dpdklab
2024-09-11 6:11 ` dpdklab
2024-09-11 6:19 ` dpdklab
2024-09-11 6:20 ` dpdklab
2024-09-11 6:22 ` dpdklab
2024-09-11 6:24 ` dpdklab
2024-09-11 6:27 ` dpdklab
2024-09-11 6:28 ` dpdklab
2024-09-11 6:29 ` dpdklab
2024-09-11 6:34 ` dpdklab
2024-09-11 6:44 ` |SUCCESS| " dpdklab
2024-09-11 7:20 ` |WARNING| " dpdklab
2024-09-11 11:45 ` |SUCCESS| " dpdklab
2024-09-11 11:51 ` dpdklab
2024-09-11 11:55 ` dpdklab [this message]
2024-09-11 12:00 ` dpdklab
2024-09-11 12:01 ` dpdklab
2024-09-11 12:19 ` dpdklab
2024-09-11 13:03 ` dpdklab
2024-09-11 17:23 ` dpdklab
2024-09-15 21:18 ` dpdklab
2024-09-16 2:51 ` 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=66e18540.170a0220.31708f.17ddSMTPIN_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).