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| pw151356-151366 [PATCH] [v5,11/11] devtools/cocci: add scr
Date: Tue, 11 Feb 2025 12:09:04 -0800 (PST)	[thread overview]
Message-ID: <67abae60.050a0220.3d2d9a.ac77SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250211173720.1188517-12-stephen@networkplumber.org>

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

_Testing PASS_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, February 11 2025 17:35:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:05db99c117e36c0cd28cda8f558309efd20055da

151356-151366 --> testing pass

Upstream job id: Template-DTS-Pipeline#212228

Test environment and result as below:

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


Ubuntu 22.04 (ARM)
	Kernel: 5.15.0-97-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/32562/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-02-11 20:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250211173720.1188517-12-stephen@networkplumber.org>
2025-02-11 17:24 ` |SUCCESS| pw151356-151366 [PATCH v5 11/11] devtools/cocci: add script to find problematic memset qemudev
2025-02-11 17:28 ` qemudev
2025-02-11 17:37 ` |SUCCESS| pw151366 " checkpatch
2025-02-11 18:45 ` 0-day Robot
2025-02-11 19:35 ` |FAILURE| pw151356-151366 [PATCH] [v5,11/11] devtools/cocci: add scr dpdklab
2025-02-11 19:45 ` |PENDING| " dpdklab
2025-02-11 19:49 ` dpdklab
2025-02-11 19:49 ` |SUCCESS| " dpdklab
2025-02-11 19:56 ` |PENDING| " dpdklab
2025-02-11 20:00 ` |SUCCESS| " dpdklab
2025-02-11 20:04 ` dpdklab
2025-02-11 20:06 ` |PENDING| " dpdklab
2025-02-11 20:09 ` dpdklab [this message]
2025-02-11 20:12 ` |SUCCESS| " dpdklab
2025-02-11 20:25 ` dpdklab
2025-02-11 20:47 ` dpdklab
2025-02-11 20:59 ` dpdklab
2025-02-11 21:10 ` dpdklab
2025-02-11 22:30 ` dpdklab
2025-02-12  1:34 ` 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=67abae60.050a0220.3d2d9a.ac77SMTPIN_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).