From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Gregory Etelson <getelson@nvidia.com>
Subject: |FAILURE| pw155028 [PATCH] bus/auxiliary: fix auxiliary device port
Date: Mon, 07 Jul 2025 04:15:53 -0700 (PDT) [thread overview]
Message-ID: <686bac69.170a0220.fcfd9.08d4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250707100648.354190-1-getelson@nvidia.com>
Test-Label: iol-sample-apps-testing
Test-Status: FAILURE
http://dpdk.org/patch/155028
_Testing issues_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Monday, July 07 2025 10:06:48
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:70c2297528e7c7789af452f78de1932e9a20c8a2
155028 --> testing issues
Upstream job id: Template-DTS-Pipeline#235498
Test environment and result as below:
+--------------+----------------------+
| Environment | compressdev_zlib_pmd |
+==============+======================+
| Ubuntu 22.04 | FAIL |
+--------------+----------------------+
==== 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) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33603/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-07-07 11:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250707100648.354190-1-getelson@nvidia.com>
2025-07-07 9:47 ` |SUCCESS| pw155028 [PATCH] bus/auxiliary: fix auxiliary device port destruction qemudev
2025-07-07 9:51 ` qemudev
2025-07-07 10:07 ` checkpatch
2025-07-07 10:56 ` |SUCCESS| pw155028 [PATCH] bus/auxiliary: fix auxiliary device port dpdklab
2025-07-07 11:03 ` |SUCCESS| pw155028 [PATCH] bus/auxiliary: fix auxiliary device port destruction 0-day Robot
2025-07-07 11:07 ` |SUCCESS| pw155028 [PATCH] bus/auxiliary: fix auxiliary device port dpdklab
2025-07-07 11:15 ` dpdklab [this message]
2025-07-07 11:18 ` dpdklab
2025-07-07 11:27 ` dpdklab
2025-07-07 11:36 ` |PENDING| " dpdklab
2025-07-07 11:38 ` dpdklab
2025-07-07 11:43 ` |FAILURE| " dpdklab
2025-07-07 11:48 ` |PENDING| " dpdklab
2025-07-07 11:56 ` dpdklab
2025-07-07 12:05 ` |SUCCESS| " dpdklab
2025-07-07 12:23 ` dpdklab
2025-07-07 12:24 ` dpdklab
2025-07-07 12:47 ` dpdklab
2025-07-07 12:58 ` |WARNING| " dpdklab
2025-07-07 13:36 ` |SUCCESS| " dpdklab
2025-07-07 13:43 ` |FAILURE| " dpdklab
2025-07-07 16:57 ` |SUCCESS| " dpdklab
2025-07-07 18:24 ` 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=686bac69.170a0220.fcfd9.08d4SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=getelson@nvidia.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).