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| pw146209-146208 [PATCH] [v2,2/2] test/power: fix power lib
Date: Fri, 18 Oct 2024 03:07:21 -0700 (PDT)	[thread overview]
Message-ID: <67123358.050a0220.8b5db.3e5dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241018033435.1305782-2-sivaprasad.tummala@amd.com>

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/146208

_Functional Testing PASS_

Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Friday, October 18 2024 03:34:35 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fe8eba692c59a92c9308f1fe429b101b9f2377bf

146209-146208 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#189246

Test environment and result as below:

Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps

Aggregate Results by Test Suite
+-----------------------------+--------+
|         Test Suite          | Result |
+=============================+========+
| unit_tests_mbuf             |  PASS  |
+-----------------------------+--------+
| vhost_virtio_user_interrupt |  PASS  |
+-----------------------------+--------+
| virtio_smoke                |  PASS  |
+-----------------------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-10-18 10:07 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241018033435.1305782-2-sivaprasad.tummala@amd.com>
2024-10-18  3:17 ` |SUCCESS| pw146209-146208 [PATCH v2 2/2] test/power: fix power library with --lcores qemudev
2024-10-18  3:22 ` qemudev
2024-10-18  3:36 ` |SUCCESS| pw146208 " checkpatch
2024-10-18  4:22 ` 0-day Robot
2024-10-18  8:20 ` |SUCCESS| pw146209-146208 [PATCH] [v2,2/2] test/power: fix power lib dpdklab
2024-10-18  8:26 ` dpdklab
2024-10-18  8:34 ` dpdklab
2024-10-18 10:07 ` dpdklab [this message]
2024-10-18 10:23 ` dpdklab
2024-10-18 10:28 ` dpdklab
2024-10-18 17:03 ` dpdklab
2024-10-18 22:34 ` dpdklab
2024-10-18 22:44 ` dpdklab
2024-10-18 22:56 ` |PENDING| " dpdklab
2024-10-18 23:09 ` dpdklab
2024-10-18 23:14 ` |SUCCESS| " dpdklab
2024-10-18 23:37 ` |PENDING| " dpdklab
2024-10-18 23:54 ` dpdklab
2024-10-19  0:04 ` dpdklab
2024-10-19  0:35 ` |SUCCESS| " dpdklab
2024-10-19  0:57 ` dpdklab
2024-10-19  1:35 ` |PENDING| " dpdklab
2024-10-19  2:06 ` |FAILURE| " dpdklab
2024-10-19  2:08 ` dpdklab
2024-10-19  2:14 ` |PENDING| " dpdklab
2024-10-19  2:19 ` |SUCCESS| " dpdklab
2024-10-19  2:20 ` dpdklab
2024-10-19  2:20 ` dpdklab
2024-10-19  2:23 ` |FAILURE| " dpdklab
2024-10-19  3:08 ` dpdklab
2024-10-19  3:09 ` dpdklab
2024-10-19  3:28 ` |SUCCESS| " dpdklab
2024-10-19  3:44 ` dpdklab
2024-10-19  4:15 ` |FAILURE| " dpdklab
2024-10-19  5:48 ` |SUCCESS| " dpdklab
2024-10-19  5:49 ` dpdklab
2024-10-19  5:49 ` dpdklab
2024-10-19  5:57 ` dpdklab
2024-10-19  6:31 ` dpdklab
2024-10-20 16:22 ` dpdklab
2024-10-20 16:50 ` dpdklab
2024-10-23  7:40 ` 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=67123358.050a0220.8b5db.3e5dSMTPIN_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).