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: |WARNING| pw155979 [PATCH] [v2] bus/vmbus: add device argument to co
Date: Mon, 18 Aug 2025 23:29:24 -0700 (PDT)	[thread overview]
Message-ID: <68a419c4.170a0220.bdd58.836fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1755563066-2592-1-git-send-email-longli@linuxonhyperv.com>

Test-Label: iol-sample-apps-testing
Test-Status: WARNING
http://dpdk.org/patch/155979

_Testing issues_

Submitter: Long Li <longli@linuxonhyperv.com>
Date: Tuesday, August 19 2025 00:24:26 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:38543d33bd47fc0ee21f59db80a8763620741879

155979 --> testing issues

Upstream job id: ACVP-FIPS-testing#10828

Test environment and result as below:

+--------------+----------------------+----------------------+
| Environment  | compressdev_zlib_pmd | dpdk_fips_validation |
+==============+======================+======================+
| Ubuntu 22.04 | PASS                 | SKIPPED              |
+--------------+----------------------+----------------------+
| Ubuntu 20.04 | SKIPPED              | WARN                 |
+--------------+----------------------+----------------------+

==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
INFO:root:Using response file...
INFO:root:Uploading response file...
INFO:root:Fetching verdict...
INFO:root:Downloading verdict for vector set 3325673
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Done
INFO:root:Using response file...
INFO:root:Uploading response file...
INFO:root:Fetching verdict...
INFO:root:Downloading verdict for vector set 3325677
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Done
INFO:root:Using response file...
INFO:root:Uploading response file...
INFO:root:Fetching verdict...
INFO:root:Downloading verdict for vector set 3325678
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Done
==== End log output ====

Ubuntu 22.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 20.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-08-19  6:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1755563066-2592-1-git-send-email-longli@linuxonhyperv.com>
2025-08-18 23:49 ` |SUCCESS| pw155979 [PATCH v2] bus/vmbus: add device argument to configure if NUMA information on the device should be ignored qemudev
2025-08-18 23:54 ` qemudev
2025-08-19  0:23 ` |WARNING| " checkpatch
2025-08-19  1:27 ` |SUCCESS| " 0-day Robot
2025-08-19  5:29 ` |SUCCESS| pw155979 [PATCH] [v2] bus/vmbus: add device argument to co dpdklab
2025-08-19  5:31 ` |PENDING| " dpdklab
2025-08-19  5:33 ` |SUCCESS| " dpdklab
2025-08-19  5:38 ` |PENDING| " dpdklab
2025-08-19  5:39 ` |SUCCESS| " dpdklab
2025-08-19  5:44 ` |PENDING| " dpdklab
2025-08-19  5:47 ` |SUCCESS| " dpdklab
2025-08-19  5:50 ` dpdklab
2025-08-19  5:52 ` dpdklab
2025-08-19  6:21 ` dpdklab
2025-08-19  6:23 ` dpdklab
2025-08-19  6:27 ` dpdklab
2025-08-19  6:29 ` dpdklab [this message]
2025-08-19  6:39 ` dpdklab
2025-08-19  7:04 ` dpdklab
2025-08-19  8:27 ` dpdklab
2025-08-19 16:27 ` dpdklab
2025-08-19 16:36 ` dpdklab
2025-08-19 16:39 ` dpdklab
2025-08-19 16:42 ` dpdklab
2025-08-19 16:49 ` dpdklab
2025-08-19 16:51 ` 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=68a419c4.170a0220.bdd58.836fSMTPIN_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).