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| pw157907 [PATCH] [v2,1/1] vfio: fix custom containers in m
Date: Tue, 21 Oct 2025 06:42:38 -0700 (PDT)	[thread overview]
Message-ID: <68f78dce.050a0220.cf645.830bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <7e195ed0245a80a7f3302ae5d3c08a66c206ca9b.1761052774.git.anatoly.burakov@intel.com>

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

_Functional Testing PASS_

Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Tuesday, October 21 2025 13:19:42 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:820ca7361bb7fa40e96e53515d8392ea40a35265

157907 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#250594

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/34339/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-10-21 13:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7e195ed0245a80a7f3302ae5d3c08a66c206ca9b.1761052774.git.anatoly.burakov@intel.com>
2025-10-21 12:53 ` |SUCCESS| pw157907 [PATCH v2 1/1] vfio: fix custom containers in multiprocess qemudev
2025-10-21 12:58 ` qemudev
2025-10-21 13:20 ` checkpatch
2025-10-21 13:41 ` |PENDING| pw157907 [PATCH] [v2,1/1] vfio: fix custom containers in m dpdklab
2025-10-21 13:42 ` dpdklab [this message]
2025-10-21 13:43 ` dpdklab
2025-10-21 13:44 ` |SUCCESS| " dpdklab
2025-10-21 13:52 ` |PENDING| " dpdklab
2025-10-21 13:57 ` dpdklab
2025-10-21 14:01 ` |SUCCESS| " dpdklab
2025-10-21 14:03 ` dpdklab
2025-10-21 14:05 ` dpdklab
2025-10-21 14:05 ` dpdklab
2025-10-21 14:08 ` dpdklab
2025-10-21 14:18 ` dpdklab
2025-10-21 14:22 ` dpdklab
2025-10-21 14:22 ` dpdklab
2025-10-21 14:26 ` |WARNING| " dpdklab
2025-10-21 14:28 ` |SUCCESS| " dpdklab
2025-10-21 15:13 ` |SUCCESS| pw157907 [PATCH v2 1/1] vfio: fix custom containers in multiprocess 0-day Robot
2025-10-21 15:13 ` 0-day Robot
2025-10-21 16:58 ` |SUCCESS| pw157907 [PATCH] [v2,1/1] vfio: fix custom containers in m dpdklab
2025-10-21 19:17 ` 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=68f78dce.050a0220.cf645.830bSMTPIN_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).