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,
	Anatoly Burakov <anatoly.burakov@intel.com>
Subject: |FAILURE| pw158952-158968 [PATCH] [v6,18/18] vfio: introduce cdev mo
Date: Fri, 21 Nov 2025 03:18:59 -0800 (PST)	[thread overview]
Message-ID: <69204aa3.050a0220.39f9ea.c738SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <fced740802ecb03dd6f1d99bf02be080e99b5148.1763719707.git.anatoly.burakov@intel.com>

Test-Label: iol-marvell-Functional
Test-Status: FAILURE
http://dpdk.org/patch/158968

_Functional Testing issues_

Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Friday, November 21 2025 10:09:03 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ef98b88455bf4a7c8b7aa3106a761c9e9270d6a3

158952-158968 --> functional testing issues

Upstream job id: Template-DTS-Pipeline#255929

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 |  FAIL  |
+----------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-11-21 11:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fced740802ecb03dd6f1d99bf02be080e99b5148.1763719707.git.anatoly.burakov@intel.com>
2025-11-21  9:41 ` |SUCCESS| pw158952-158968 [PATCH v6 18/18] vfio: introduce cdev mode qemudev
2025-11-21  9:46 ` qemudev
2025-11-21 10:13 ` |SUCCESS| pw158968 " checkpatch
2025-11-21 11:09 ` |PENDING| pw158952-158968 [PATCH] [v6,18/18] vfio: introduce cdev mo dpdklab
2025-11-21 11:15 ` dpdklab
2025-11-21 11:18 ` dpdklab [this message]
2025-11-21 11:21 ` |SUCCESS| " dpdklab
2025-11-21 11:25 ` dpdklab
2025-11-21 11:33 ` dpdklab
2025-11-21 11:42 ` |PENDING| " dpdklab
2025-11-21 11:49 ` |SUCCESS| " dpdklab
2025-11-21 12:04 ` dpdklab
2025-11-21 12:08 ` dpdklab
2025-11-21 12:08 ` dpdklab
2025-11-21 12:10 ` |FAILURE| " dpdklab
2025-11-21 12:25 ` |SUCCESS| " dpdklab
2025-11-21 12:30 ` 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=69204aa3.050a0220.39f9ea.c738SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=anatoly.burakov@intel.com \
    --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).