automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Georgii Tkachuk <georgii.tkachuk@intel.com>,
	Qian Xu <qian.q.xu@intel.com>, Lijuan Tu <lijuan.tu@intel.com>,
	Test Report <test-report@dpdk.org>,
	Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-test-reports@iol.unh.edu,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: |FAILURE| pw159155-159168 [PATCH] [RFC,v2,14/14] lib: enable format
Date: Fri, 05 Dec 2025 01:36:40 -0800 (PST)	[thread overview]
Message-ID: <6932a7a8.050a0220.8e2d.0afbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251205022948.327743-15-stephen@networkplumber.org>

Test-Label: iol-intel-Functional
Test-Status: FAILURE
http://dpdk.org/patch/159168

_Functional Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, December 05 2025 02:28:23 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:80b3e9cad7599ce01f94cd6f8f966401a77e29c1

159155-159168 --> functional testing issues

Upstream job id: Template-DTS-Pipeline#257562

Test environment and result as below:

Ubuntu 20.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 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                |  FAIL  |
+-----------------------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-12-05  9:36 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251205022948.327743-15-stephen@networkplumber.org>
2025-12-05  2:03 ` |SUCCESS| pw159155-159168 [RFC v2 14/14] lib: enable format overflow warnings qemudev
2025-12-05  2:11 ` |FAILURE| " qemudev
2025-12-05  2:30 ` |SUCCESS| pw159168 " checkpatch
2025-12-05  3:24 ` |FAILURE| " 0-day Robot
2025-12-05  6:28 ` |FAILURE| pw159155-159168 [PATCH] [RFC,v2,14/14] lib: enable format dpdklab
2025-12-05  6:31 ` dpdklab
2025-12-05  6:37 ` |SUCCESS| " dpdklab
2025-12-05  7:04 ` |PENDING| " dpdklab
2025-12-05  7:05 ` |SUCCESS| " dpdklab
2025-12-05  7:33 ` dpdklab
2025-12-05  9:13 ` |WARNING| " dpdklab
2025-12-05  9:34 ` dpdklab
2025-12-05  9:36 ` dpdklab [this message]
2025-12-05 11:18 ` dpdklab
2025-12-05 11:26 ` |FAILURE| " dpdklab
2025-12-05 11:55 ` dpdklab
2025-12-05 12:03 ` dpdklab
2025-12-05 12:28 ` dpdklab
2025-12-05 12:47 ` dpdklab
2025-12-05 12:49 ` dpdklab
2025-12-05 16:18 ` |SUCCESS| " dpdklab
2025-12-05 16:32 ` |FAILURE| " dpdklab
2025-12-05 16:51 ` |WARNING| " dpdklab
2025-12-05 23:02 ` |SUCCESS| " dpdklab
2025-12-05 23:18 ` dpdklab
2025-12-06  0:52 ` |FAILURE| " dpdklab
2025-12-06  1:16 ` dpdklab
2025-12-06  1:17 ` dpdklab
2025-12-06  1:19 ` dpdklab
2025-12-06  1:30 ` dpdklab
2025-12-06  2:24 ` dpdklab
2025-12-06  2:51 ` dpdklab
2025-12-06  5:11 ` dpdklab
2025-12-06  5:11 ` dpdklab
2025-12-06  5:11 ` dpdklab
2025-12-06  5:12 ` dpdklab
2025-12-06  5:12 ` dpdklab
2025-12-06  5:13 ` dpdklab
2025-12-06  5:13 ` dpdklab
2025-12-06  5:15 ` dpdklab
2025-12-06  5:17 ` dpdklab
2025-12-06  5:18 ` dpdklab
2025-12-06  5:20 ` dpdklab
2025-12-06  5:22 ` dpdklab
2025-12-06  6:04 ` dpdklab
2025-12-06  6:05 ` dpdklab
2025-12-06  6:06 ` |WARNING| " dpdklab
2025-12-06 12:22 ` |FAILURE| " 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=6932a7a8.050a0220.8e2d.0afbSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@intel.com \
    --cc=georgii.tkachuk@intel.com \
    --cc=lijuan.tu@intel.com \
    --cc=qian.q.xu@intel.com \
    --cc=stephen@networkplumber.org \
    --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).