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| pw138489-138488 [PATCH] [2/2] examples/l3fwd-power: add PM
Date: Wed, 20 Mar 2024 04:53:50 -0700 (PDT)	[thread overview]
Message-ID: <65face4e.050a0220.7a186.d37cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240320105529.5626-3-lihuisong@huawei.com>

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138488

_Testing PASS_

Submitter: Huisong Li <lihuisong@huawei.com>
Date: Wednesday, March 20 2024 10:55:29 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2

138489-138488 --> testing pass

Test environment and result as below:

+--------------------------+----------------+
|       Environment        | dpdk_unit_test |
+==========================+================+
| Debian 11 (Buster) (ARM) | PASS           |
+--------------------------+----------------+
| Fedora 37 (ARM)          | PASS           |
+--------------------------+----------------+
| Debian 12 (arm)          | PASS           |
+--------------------------+----------------+
| CentOS Stream 9 (ARM)    | PASS           |
+--------------------------+----------------+


Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 11

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.1

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

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-20 11:53 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240320105529.5626-3-lihuisong@huawei.com>
2024-03-20 10:40 ` |SUCCESS| pw138489-138488 [PATCH 2/2] examples/l3fwd-power: add PM QoS request configuration qemudev
2024-03-20 10:45 ` qemudev
2024-03-20 11:03 ` |SUCCESS| pw138488 " checkpatch
2024-03-20 11:45 ` |SUCCESS| pw138489-138488 [PATCH] [2/2] examples/l3fwd-power: add PM dpdklab
2024-03-20 11:46 ` dpdklab
2024-03-20 11:46 ` dpdklab
2024-03-20 11:46 ` dpdklab
2024-03-20 11:46 ` dpdklab
2024-03-20 11:46 ` dpdklab
2024-03-20 11:46 ` dpdklab
2024-03-20 11:47 ` dpdklab
2024-03-20 11:47 ` dpdklab
2024-03-20 11:47 ` dpdklab
2024-03-20 11:47 ` dpdklab
2024-03-20 11:47 ` dpdklab
2024-03-20 11:48 ` dpdklab
2024-03-20 11:48 ` dpdklab
2024-03-20 11:48 ` dpdklab
2024-03-20 11:48 ` dpdklab
2024-03-20 11:49 ` dpdklab
2024-03-20 11:49 ` dpdklab
2024-03-20 11:49 ` dpdklab
2024-03-20 11:49 ` dpdklab
2024-03-20 11:49 ` dpdklab
2024-03-20 11:49 ` dpdklab
2024-03-20 11:50 ` dpdklab
2024-03-20 11:50 ` dpdklab
2024-03-20 11:50 ` dpdklab
2024-03-20 11:50 ` dpdklab
2024-03-20 11:50 ` dpdklab
2024-03-20 11:51 ` dpdklab
2024-03-20 11:51 ` dpdklab
2024-03-20 11:51 ` dpdklab
2024-03-20 11:51 ` dpdklab
2024-03-20 11:51 ` dpdklab
2024-03-20 11:52 ` dpdklab
2024-03-20 11:52 ` dpdklab
2024-03-20 11:52 ` dpdklab
2024-03-20 11:52 ` dpdklab
2024-03-20 11:52 ` dpdklab
2024-03-20 11:53 ` dpdklab
2024-03-20 11:53 ` dpdklab
2024-03-20 11:53 ` dpdklab
2024-03-20 11:53 ` dpdklab
2024-03-20 11:53 ` dpdklab [this message]
2024-03-20 11:54 ` dpdklab
2024-03-20 11:54 ` dpdklab
2024-03-20 11:54 ` dpdklab
2024-03-20 11:54 ` dpdklab
2024-03-20 11:54 ` dpdklab
2024-03-20 11:54 ` dpdklab
2024-03-20 11:54 ` dpdklab
2024-03-20 11:55 ` dpdklab
2024-03-20 11:55 ` dpdklab
2024-03-20 11:55 ` dpdklab
2024-03-20 11:55 ` dpdklab
2024-03-20 11:55 ` dpdklab
2024-03-20 11:55 ` dpdklab
2024-03-20 11:56 ` dpdklab
2024-03-20 11:56 ` dpdklab
2024-03-20 11:57 ` dpdklab
2024-03-20 11:57 ` dpdklab
2024-03-20 11:57 ` dpdklab
2024-03-20 11:57 ` dpdklab
2024-03-20 11:57 ` dpdklab
2024-03-20 11:58 ` dpdklab
2024-03-20 11:58 ` dpdklab
2024-03-20 11:59 ` dpdklab
2024-03-20 12:01 ` dpdklab
2024-03-20 12:03 ` dpdklab
2024-03-20 12:06 ` dpdklab
2024-03-20 12:06 ` dpdklab
2024-03-20 12:09 ` dpdklab
2024-03-20 12:43 ` |SUCCESS| pw138488 [PATCH 2/2] examples/l3fwd-power: add PM QoS request configuration 0-day Robot
2024-03-20 12:45 ` |SUCCESS| pw138489-138488 [PATCH] [2/2] examples/l3fwd-power: add PM dpdklab
2024-03-20 13:03 ` dpdklab
2024-03-21  6:33 ` dpdklab
2024-03-22  0:29 ` dpdklab
2024-03-22  1:04 ` 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=65face4e.050a0220.7a186.d37cSMTPIN_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).