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| pw144185-144227 [PATCH] [v2,43/43] net/dpaa2: dpdmux singl
Date: Wed, 18 Sep 2024 19:24:14 -0700 (PDT)	[thread overview]
Message-ID: <66eb8b4e.c80a0220.1e55f1.1b0fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240918075056.1838654-44-vanshika.shukla@nxp.com>

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

_Testing issues_

Submitter: None <vanshika.shukla@nxp.com>
Date: Wednesday, September 18 2024 07:50:56 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

144185-144227 --> testing issues

Upstream job id: ACVP-FIPS-testing#6981

Test environment and result as below:

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

==== 20 line log output for Ubuntu 22.04 (ARM) (compressdev_zlib_pmd): ====
 --- Failed to get log output --- 
==== 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: 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/31058/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-19  2:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240918075056.1838654-44-vanshika.shukla@nxp.com>
2024-09-18  7:31 ` |SUCCESS| pw144185-144227 [v2 43/43] net/dpaa2: dpdmux single flow/multiple rules support qemudev
2024-09-18  7:36 ` qemudev
2024-09-18  7:59 ` |WARNING| pw144227 " checkpatch
2024-09-18  8:44 ` |SUCCESS| " 0-day Robot
2024-09-18 11:19 ` |SUCCESS| pw144185-144227 [PATCH] [v2,43/43] net/dpaa2: dpdmux singl dpdklab
2024-09-18 11:33 ` dpdklab
2024-09-18 11:40 ` |WARNING| " dpdklab
2024-09-18 11:43 ` |SUCCESS| " dpdklab
2024-09-18 11:50 ` dpdklab
2024-09-18 12:14 ` |WARNING| " dpdklab
2024-09-18 13:48 ` |SUCCESS| " dpdklab
2024-09-18 14:27 ` dpdklab
2024-09-18 14:41 ` dpdklab
2024-09-18 14:48 ` dpdklab
2024-09-18 14:49 ` dpdklab
2024-09-18 14:54 ` dpdklab
2024-09-18 14:54 ` dpdklab
2024-09-18 14:55 ` dpdklab
2024-09-18 14:55 ` dpdklab
2024-09-18 14:56 ` dpdklab
2024-09-18 16:17 ` dpdklab
2024-09-19  2:24 ` dpdklab [this message]
2024-09-22 13:47 ` dpdklab
2024-09-22 13:59 ` 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=66eb8b4e.c80a0220.1e55f1.1b0fSMTPIN_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).