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,
	Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: |SUCCESS| [GIT MASTER] bfb6c9fbcbaada197af422b704cf71b777f85fff
Date: Fri, 31 Oct 2025 09:30:43 -0700 (PDT)	[thread overview]
Message-ID: <6904e433.170a0220.db04c.3938SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: next-net-brcm-for-next-net

bfb6c9fbcbaada197af422b704cf71b777f85fff --> testing pass

Upstream job id: Template-DTS-Pipeline#252316

Test environment and result as below:

+--------------+----------------------+
| Environment  | compressdev_zlib_pmd |
+==============+======================+
| Ubuntu 22.04 | PASS                 |
+--------------+----------------------+


Ubuntu 22.04
	Kernel: 5.15
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04.2) 11.4.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/35413/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2025-10-31 16:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31 16:30 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-10-31 21:33 dpdklab
2025-10-31 20:45 dpdklab
2025-10-31 17:39 dpdklab
2025-10-31 17:34 dpdklab
2025-10-31 17:34 dpdklab
2025-10-31 17:27 dpdklab
2025-10-31 16:53 dpdklab
2025-10-31 16:53 dpdklab
2025-10-31 16:49 dpdklab
2025-10-31 16:43 dpdklab
2025-10-31 16:31 dpdklab
2025-10-31 16:22 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=6904e433.170a0220.db04c.3938SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=ajit.khaparde@broadcom.com \
    --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).