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| pw153460 [PATCH] [RFC] dts: add rte flow test suite
Date: Wed, 11 Jun 2025 08:16:09 -0700 (PDT)	[thread overview]
Message-ID: <68499db9.050a0220.19bc1.4825SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250515163809.184720-2-dmarx@iol.unh.edu>

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

_Testing issues_

Submitter: Dean Marx <dmarx@iol.unh.edu>
Date: Thursday, May 15 2025 16:38:09 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:1aef42bc97a31906486c9d66b792208948af06f3

153460 --> testing issues

Upstream job id: Template-DTS-Pipeline#226031

Test environment and result as below:

+--------------------+----------------------+----------------------+
|    Environment     | compressdev_zlib_pmd | dpdk_fips_validation |
+====================+======================+======================+
| Ubuntu 22.04       | PASS                 | SKIPPED              |
+--------------------+----------------------+----------------------+
| Ubuntu 22.04 (ARM) | 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 3129792
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 3129794
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 3129795
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
	Kernel: 5.15.0-100-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 22.04 (ARM)
	Kernel: 5.15.0-97-generic
	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/33183/

UNH-IOL DPDK Community Lab

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

      parent reply	other threads:[~2025-06-11 15:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250515163809.184720-2-dmarx@iol.unh.edu>
2025-05-15 16:05 ` |SUCCESS| pw153460 [RFC PATCH] " qemudev
2025-05-15 16:09 ` qemudev
2025-05-15 16:40 ` |WARNING| " checkpatch
2025-05-15 17:43 ` |SUCCESS| " 0-day Robot
2025-05-15 19:17 ` |SUCCESS| pw153460 [PATCH] [RFC] " dpdklab
2025-05-15 19:30 ` dpdklab
2025-05-15 19:31 ` dpdklab
2025-05-15 19:38 ` dpdklab
2025-05-15 19:45 ` dpdklab
2025-05-15 19:45 ` dpdklab
2025-05-15 19:51 ` dpdklab
2025-05-15 20:14 ` dpdklab
2025-05-15 20:18 ` dpdklab
2025-05-15 20:42 ` |PENDING| " dpdklab
2025-05-15 20:58 ` |SUCCESS| " dpdklab
2025-05-15 21:52 ` dpdklab
2025-05-15 22:11 ` dpdklab
2025-05-15 23:11 ` |PENDING| " dpdklab
2025-05-15 23:37 ` dpdklab
2025-05-15 23:42 ` dpdklab
2025-05-16  0:17 ` |SUCCESS| " dpdklab
2025-05-16  0:31 ` dpdklab
2025-05-16  0:36 ` dpdklab
2025-05-16  0:36 ` dpdklab
2025-05-16  9:22 ` |WARNING| " dpdklab
2025-06-11 15:16 ` 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=68499db9.050a0220.19bc1.4825SMTPIN_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).