automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138458-138462 [PATCH] [v5,6/6] examples/vm_power_manager
Date: Mon, 18 Mar 2024 13:08:47 -0700 (PDT)	[thread overview]
Message-ID: <65f89f4f.050a0220.c2e2.ad8fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240318173146.24303-7-sivaprasad.tummala@amd.com>

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138462

_Functional Testing PASS_

Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Monday, March 18 2024 17:31:45 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2

138458-138462 --> 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


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-82
Compiler: gcc 11.4.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/1


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29584/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-03-18 20:08 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240318173146.24303-7-sivaprasad.tummala@amd.com>
2024-03-18 17:11 ` |SUCCESS| pw138458-138462 [PATCH v5 6/6] examples/vm_power_manager: fix lcore ID restriction qemudev
2024-03-18 17:16 ` qemudev
2024-03-18 17:34 ` |SUCCESS| pw138462 " checkpatch
2024-03-18 18:23 ` 0-day Robot
2024-03-18 19:59 ` |SUCCESS| pw138458-138462 [PATCH] [v5,6/6] examples/vm_power_manager dpdklab
2024-03-18 20:00 ` dpdklab
2024-03-18 20:00 ` dpdklab
2024-03-18 20:01 ` dpdklab
2024-03-18 20:03 ` dpdklab
2024-03-18 20:03 ` dpdklab
2024-03-18 20:04 ` dpdklab
2024-03-18 20:08 ` dpdklab [this message]
2024-03-18 20:12 ` dpdklab
2024-03-18 20:16 ` dpdklab
2024-03-18 20:17 ` dpdklab
2024-03-18 20:17 ` dpdklab
2024-03-18 20:19 ` dpdklab
2024-03-18 20:19 ` dpdklab
2024-03-18 20:19 ` dpdklab
2024-03-18 20:20 ` dpdklab
2024-03-18 20:30 ` dpdklab
2024-03-18 20:32 ` dpdklab
2024-03-18 20:32 ` dpdklab
2024-03-18 20:33 ` dpdklab
2024-03-18 20:33 ` dpdklab
2024-03-18 20:34 ` dpdklab
2024-03-18 20:35 ` dpdklab
2024-03-18 20:36 ` dpdklab
2024-03-18 20:37 ` dpdklab
2024-03-18 20:37 ` dpdklab
2024-03-18 20:38 ` dpdklab
2024-03-18 20:38 ` dpdklab
2024-03-18 20:38 ` dpdklab
2024-03-18 20:39 ` dpdklab
2024-03-18 20:39 ` dpdklab
2024-03-18 20:39 ` dpdklab
2024-03-18 20:39 ` dpdklab
2024-03-18 20:40 ` dpdklab
2024-03-18 20:40 ` dpdklab
2024-03-18 20:41 ` dpdklab
2024-03-18 20:41 ` dpdklab
2024-03-18 20:41 ` dpdklab
2024-03-18 20:41 ` dpdklab
2024-03-18 20:41 ` dpdklab
2024-03-18 20:42 ` dpdklab
2024-03-18 20:42 ` dpdklab
2024-03-18 20:42 ` dpdklab
2024-03-18 20:42 ` dpdklab
2024-03-18 20:42 ` dpdklab
2024-03-18 20:43 ` dpdklab
2024-03-18 20:43 ` dpdklab
2024-03-18 20:43 ` dpdklab
2024-03-18 20:43 ` dpdklab
2024-03-18 20:43 ` dpdklab
2024-03-18 20:43 ` dpdklab
2024-03-18 20:44 ` dpdklab
2024-03-18 20:44 ` dpdklab
2024-03-18 20:44 ` dpdklab
2024-03-18 20:44 ` dpdklab
2024-03-18 20:44 ` dpdklab
2024-03-18 20:44 ` dpdklab
2024-03-18 20:44 ` dpdklab
2024-03-18 20:45 ` dpdklab
2024-03-18 20:45 ` dpdklab
2024-03-18 20:45 ` dpdklab
2024-03-18 20:45 ` dpdklab
2024-03-18 20:45 ` dpdklab
2024-03-18 20:45 ` dpdklab
2024-03-18 20:45 ` dpdklab
2024-03-18 20:46 ` dpdklab
2024-03-18 20:51 ` dpdklab
2024-03-18 20:56 ` dpdklab
2024-03-18 21:01 ` |FAILURE| " dpdklab
2024-03-18 21:02 ` |SUCCESS| " dpdklab
2024-03-18 21:14 ` |FAILURE| " dpdklab
2024-03-18 21:20 ` |SUCCESS| " dpdklab
2024-03-18 21:22 ` dpdklab
2024-03-18 23:31 ` dpdklab
2024-03-20 19:39 ` dpdklab
2024-03-20 20:13 ` 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=65f89f4f.050a0220.c2e2.ad8fSMTPIN_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).