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: |SUCCESS| pw152847-152848 [PATCH] [v5,3/3] hash_readwrite_autotest:
Date: Tue, 08 Apr 2025 19:55:30 -0700 (PDT)	[thread overview]
Message-ID: <67f5e1a2.050a0220.12c19b.0a36SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1744161658-7874-4-git-send-email-andremue@linux.microsoft.com>

Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/152848

_Testing PASS_

Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Wednesday, April 09 2025 01:20:58 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:8ee74a69abcf48563f05adeafecd298bb03477a8

152847-152848 --> testing pass

Upstream job id: Template-DTS-Pipeline#220821

Test environment and result as below:

+--------------------+----------------------+
|    Environment     | compressdev_zlib_pmd |
+====================+======================+
| Ubuntu 22.04 (ARM) | PASS                 |
+--------------------+----------------------+
| Ubuntu 22.04       | PASS                 |
+--------------------+----------------------+


Ubuntu 22.04 (ARM)
	Kernel: 5.15.0-97-generic
	Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0

Ubuntu 22.04
	Kernel: 5.15.0-100-generic
	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/32975/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-04-09  2:55 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1744161658-7874-4-git-send-email-andremue@linux.microsoft.com>
2025-04-09  0:47 ` |SUCCESS| pw152847-152848 [PATCH v5 3/3] hash_readwrite_autotest: fix printf parameters qemudev
2025-04-09  0:51 ` qemudev
2025-04-09  1:22 ` |SUCCESS| pw152848 " checkpatch
2025-04-09  1:51 ` |SUCCESS| pw152847-152848 [PATCH] [v5,3/3] hash_readwrite_autotest: dpdklab
2025-04-09  1:57 ` dpdklab
2025-04-09  2:00 ` dpdklab
2025-04-09  2:04 ` |PENDING| " dpdklab
2025-04-09  2:05 ` |SUCCESS| " dpdklab
2025-04-09  2:06 ` |PENDING| " dpdklab
2025-04-09  2:10 ` dpdklab
2025-04-09  2:10 ` |SUCCESS| " dpdklab
2025-04-09  2:20 ` dpdklab
2025-04-09  2:23 ` dpdklab
2025-04-09  2:30 ` |PENDING| " dpdklab
2025-04-09  2:38 ` |SUCCESS| " dpdklab
2025-04-09  2:43 ` |SUCCESS| pw152848 [PATCH v5 3/3] hash_readwrite_autotest: fix printf parameters 0-day Robot
2025-04-09  2:55 ` dpdklab [this message]
2025-04-09  3:13 ` |SUCCESS| pw152847-152848 [PATCH] [v5,3/3] hash_readwrite_autotest: dpdklab
2025-04-09  3:17 ` dpdklab
2025-04-09  3:17 ` dpdklab
2025-04-09  3:18 ` dpdklab
2025-04-09  4:15 ` dpdklab
2025-04-09  4:23 ` dpdklab
2025-04-09  4:27 ` dpdklab
2025-04-09  5:32 ` dpdklab
2025-04-09  5:44 ` dpdklab
2025-04-09  7:28 ` dpdklab
2025-04-10 23:06 ` dpdklab
2025-04-10 23: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=67f5e1a2.050a0220.12c19b.0a36SMTPIN_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).