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| pw151040 [PATCH] vhost: fix FD entries cleanup
Date: Sat, 08 Feb 2025 08:32:47 -0800 (PST)	[thread overview]
Message-ID: <67a7872f.050a0220.177405.08c1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250206084154.2230766-1-maxime.coquelin@redhat.com>

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

_Testing issues_

Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Thursday, February 06 2025 08:41:54 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d92688baedcfc963b7539899347012a09c45a15b

151040 --> testing issues

Upstream job id: ACVP-FIPS-testing#8810

Test environment and result as below:

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

==== 20 line log output for Ubuntu 20.04 (dpdk_fips_validation): ====
INFO:root:Fetching verdict...
INFO:root:Downloading verdict for vector set 2879297
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 2879298
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 2879299
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Vector set verdict not ready, waiting 30 seconds...
INFO:root:Done
==== End log output ====

Ubuntu 22.04 (ARM)
	Kernel: 5.15.0-97-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 22.04
	Kernel: 5.15.0-100-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 20.04
	Kernel: Depends on container host
	Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

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

UNH-IOL DPDK Community Lab

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

      parent reply	other threads:[~2025-02-08 16:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250206084154.2230766-1-maxime.coquelin@redhat.com>
2025-02-06  8:07 ` |SUCCESS| " qemudev
2025-02-06  8:11 ` qemudev
2025-02-06  8:42 ` |WARNING| " checkpatch
2025-02-06  9:44 ` |SUCCESS| " dpdklab
2025-02-06  9:45 ` 0-day Robot
2025-02-06  9:49 ` dpdklab
2025-02-06  9:58 ` dpdklab
2025-02-06 10:00 ` dpdklab
2025-02-06 10:11 ` dpdklab
2025-02-06 10:13 ` |PENDING| " dpdklab
2025-02-06 10:15 ` dpdklab
2025-02-06 10:16 ` |SUCCESS| " dpdklab
2025-02-06 13:39 ` |PENDING| " dpdklab
2025-02-06 14:22 ` |SUCCESS| " dpdklab
2025-02-06 17:37 ` dpdklab
2025-02-06 18:49 ` |PENDING| " dpdklab
2025-02-06 19:53 ` |SUCCESS| " dpdklab
2025-02-06 22:54 ` dpdklab
2025-02-07 12:49 ` dpdklab
2025-02-07 13:11 ` dpdklab
2025-02-08 13:53 ` dpdklab
2025-02-08 14:06 ` dpdklab
2025-02-08 16:32 ` dpdklab [this message]

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=67a7872f.050a0220.177405.08c1SMTPIN_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).