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| pw158869-158888 [PATCH] [v3,20/20] vfio: introduce cdev mo
Date: Tue, 18 Nov 2025 10:20:20 -0800 (PST) [thread overview]
Message-ID: <691cb8e4.050a0220.25fd18.cd59SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <7e49d0a3938ca536b188241cf6950a6bf901f1f0.1763483254.git.anatoly.burakov@intel.com>
Test-Label: iol-marvell-Functional
Test-Status: FAILURE
http://dpdk.org/patch/158888
_Functional Testing issues_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Tuesday, November 18 2025 16:29:21
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a0b148048b3d9960788093b3b94c70af8f04136b
158869-158888 --> functional testing issues
Upstream job id: Template-DTS-Pipeline#255607
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/34632/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-11-18 18:20 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7e49d0a3938ca536b188241cf6950a6bf901f1f0.1763483254.git.anatoly.burakov@intel.com>
2025-11-18 15:58 ` |SUCCESS| pw158869-158888 [PATCH v3 20/20] vfio: introduce cdev mode qemudev
2025-11-18 16:03 ` qemudev
2025-11-18 16:32 ` |SUCCESS| pw158888 " checkpatch
2025-11-18 17:52 ` |FAILURE| " 0-day Robot
2025-11-18 18:14 ` |PENDING| pw158869-158888 [PATCH] [v3,20/20] vfio: introduce cdev mo dpdklab
2025-11-18 18:15 ` |SUCCESS| " dpdklab
2025-11-18 18:15 ` |FAILURE| " dpdklab
2025-11-18 18:15 ` |PENDING| " dpdklab
2025-11-18 18:16 ` |FAILURE| " dpdklab
2025-11-18 18:16 ` dpdklab
2025-11-18 18:20 ` dpdklab [this message]
2025-11-18 18:23 ` |PENDING| " dpdklab
2025-11-18 18:34 ` |FAILURE| " dpdklab
2025-11-18 18:34 ` |SUCCESS| " dpdklab
2025-11-18 18:35 ` dpdklab
2025-11-18 18:49 ` dpdklab
2025-11-18 18:51 ` |FAILURE| " dpdklab
2025-11-18 19:05 ` |SUCCESS| " dpdklab
2025-11-18 19:07 ` dpdklab
2025-11-18 19:18 ` dpdklab
2025-11-18 20:17 ` |FAILURE| " dpdklab
2025-11-18 20:19 ` dpdklab
2025-11-18 20:21 ` dpdklab
2025-11-18 20:23 ` dpdklab
2025-11-18 20:24 ` dpdklab
2025-11-18 20:25 ` dpdklab
2025-11-18 20:27 ` dpdklab
2025-11-18 20:28 ` dpdklab
2025-11-18 20:30 ` dpdklab
2025-11-18 20:31 ` dpdklab
2025-11-18 20:31 ` dpdklab
2025-11-18 20:32 ` dpdklab
2025-11-18 20:33 ` dpdklab
2025-11-18 20:34 ` |WARNING| " 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=691cb8e4.050a0220.25fd18.cd59SMTPIN_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).