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, Akhil Goyal <gakhil@marvell.com>,
	Sameer Vaze <svaze@qti.qualcomm.com>
Subject: |FAILURE| pw156779-156777 [PATCH] [3/3] app/compres-perf: support fo
Date: Fri, 19 Sep 2025 11:56:03 -0700 (PDT)	[thread overview]
Message-ID: <68cda743.050a0220.2ec9f8.0e56SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250919172802.2461479-3-svaze@qti.qualcomm.com>

Test-Label: iol-sample-apps-testing
Test-Status: FAILURE
http://dpdk.org/patch/156777

_Testing issues_

Submitter: Sameer Vaze <svaze@qti.qualcomm.com>
Date: Friday, September 19 2025 17:28:02 
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: master
  CommitID:4159ea62922ce41566c7bab44655ad78bee85458

156779-156777 --> testing issues

Upstream job id: Template-DTS-Pipeline#245465

Test environment and result as below:

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

==== 20 line log output for Ubuntu 22.04 (compressdev_zlib_pmd): ====
 --- Failed to get log output --- 
==== End log output ====

Ubuntu 22.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 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/34110/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-09-19 18:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250919172802.2461479-3-svaze@qti.qualcomm.com>
2025-09-19 16:53 ` |SUCCESS| pw156779-156777 [PATCH 3/3] app/compres-perf: support for dictionaries and PDCP checksum qemudev
2025-09-19 16:58 ` qemudev
2025-09-19 17:26 ` |SUCCESS| pw156777 " checkpatch
2025-09-19 17:50 ` |FAILURE| pw156779-156777 [PATCH] [3/3] app/compres-perf: support fo dpdklab
2025-09-19 17:55 ` dpdklab
2025-09-19 17:55 ` |SUCCESS| " dpdklab
2025-09-19 17:59 ` dpdklab
2025-09-19 18:02 ` |FAILURE| " dpdklab
2025-09-19 18:12 ` |SUCCESS| " dpdklab
2025-09-19 18:14 ` |PENDING| " dpdklab
2025-09-19 18:15 ` |SUCCESS| " dpdklab
2025-09-19 18:24 ` |FAILURE| " dpdklab
2025-09-19 18:39 ` dpdklab
2025-09-19 18:41 ` |WARNING| " dpdklab
2025-09-19 18:47 ` dpdklab
2025-09-19 18:49 ` |SUCCESS| " dpdklab
2025-09-19 18:56 ` dpdklab [this message]
2025-09-19 18:59 ` |FAILURE| pw156777 [PATCH 3/3] app/compres-perf: support for dictionaries and PDCP checksum 0-day Robot
2025-09-19 19:25 ` |FAILURE| pw156779-156777 [PATCH] [3/3] app/compres-perf: support fo dpdklab
2025-09-19 19:27 ` |SUCCESS| " dpdklab
2025-09-19 19:41 ` dpdklab
2025-09-19 20:09 ` 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=68cda743.050a0220.2ec9f8.0e56SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=gakhil@marvell.com \
    --cc=svaze@qti.qualcomm.com \
    --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).