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| pw152304-152309 [PATCH] [v2,6/6] bus/vmbus: set event for
Date: Tue, 11 Mar 2025 02:33:18 -0700 (PDT)	[thread overview]
Message-ID: <67d0035e.050a0220.761d1.57c8SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1741642977-14297-7-git-send-email-longli@linuxonhyperv.com>

Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/152309

_Functional Testing PASS_

Submitter: Long Li <longli@linuxonhyperv.com>
Date: Monday, March 10 2025 21:42:57 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d59e5e7d3e827f02131a88bafd9191efd6720a42

152304-152309 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#217134

Test environment and result as below:

Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc

Aggregate Results by Test Suite
+----------------+--------+
|   Test Suite   | Result |
+================+========+
| cmdline        |  PASS  |
+----------------+--------+
| rxtx_callbacks |  PASS  |
+----------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-03-11  9:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1741642977-14297-7-git-send-email-longli@linuxonhyperv.com>
2025-03-10 21:28 ` |SUCCESS| pw152304-152309 [patch v2 6/6] bus/vmbus: set event for channel without monitoring support qemudev
2025-03-10 21:32 ` qemudev
2025-03-10 21:44 ` |WARNING| pw152309 " checkpatch
2025-03-10 22:43 ` |FAILURE| " 0-day Robot
2025-03-11  9:33 ` dpdklab [this message]
2025-03-11  9:42 ` |SUCCESS| pw152304-152309 [PATCH] [v2,6/6] bus/vmbus: set event for dpdklab
2025-03-11  9:47 ` dpdklab
2025-03-11 10:00 ` dpdklab
2025-03-11 10:11 ` dpdklab
2025-03-11 10:15 ` dpdklab
2025-03-11 10:21 ` dpdklab
2025-03-11 10:32 ` dpdklab
2025-03-11 10:44 ` dpdklab
2025-03-11 10:45 ` |PENDING| " dpdklab
2025-03-11 11:01 ` |WARNING| " dpdklab
2025-03-11 11:08 ` |SUCCESS| " dpdklab
2025-03-11 11:41 ` dpdklab
2025-03-11 11:51 ` |WARNING| " dpdklab
2025-03-11 11:53 ` |SUCCESS| " dpdklab
2025-03-11 11:53 ` |WARNING| " dpdklab
2025-03-11 11:54 ` dpdklab
2025-03-11 12:01 ` |SUCCESS| " dpdklab
2025-03-11 12:02 ` dpdklab
2025-03-11 13:19 ` dpdklab
2025-03-11 13:21 ` 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=67d0035e.050a0220.761d1.57c8SMTPIN_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).