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| pw152931-152932 [PATCH] [2/2] dts: use tmp dir and DPDK tr
Date: Tue, 15 Apr 2025 16:41:10 -0700 (PDT)	[thread overview]
Message-ID: <67feee96.d40a0220.1a8ec0.2cdeSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250415130903.224858-3-thomas.wilks@arm.com>

Test-Label: iol-dts-check-format-testing
Test-Status: SUCCESS
http://dpdk.org/patch/152932

_Testing PASS_

Submitter: Thomas Wilks <thomas.wilks@arm.com>
Date: Tuesday, April 15 2025 13:09:03 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:c933d60a7f8696695eb08ae655f2d809aedc29d5

152931-152932 --> testing pass

Upstream job id: DTS-Check-Format-Pipeline#41

Test environment and result as below:

+--------------------+------------------+
|    Environment     | dts-check-format |
+====================+==================+
| Ubuntu 22.04.5 LTS | PASS             |
+--------------------+------------------+


Ubuntu 22.04.5 LTS
	Kernel: 5.15.0-119-generic
	Compiler: gcc 11.4.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33011/

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-15 23:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250415130903.224858-3-thomas.wilks@arm.com>
2025-04-15 12:41 ` |SUCCESS| pw152931-152932 [PATCH 2/2] dts: use tmp dir and DPDK tree dir qemudev
2025-04-15 12:45 ` qemudev
2025-04-15 13:10 ` |SUCCESS| pw152932 " checkpatch
2025-04-15 14:23 ` 0-day Robot
2025-04-15 23:41 ` dpdklab [this message]
2025-04-15 23:43 ` |SUCCESS| pw152931-152932 [PATCH] [2/2] dts: use tmp dir and DPDK tr dpdklab
2025-04-16  0:02 ` dpdklab
2025-04-16  0:08 ` dpdklab
2025-04-16  0:11 ` dpdklab
2025-04-16  0:14 ` dpdklab
2025-04-16  0:14 ` dpdklab
2025-04-16  0:25 ` dpdklab
2025-04-16  0:28 ` dpdklab
2025-04-16  0:30 ` |PENDING| " dpdklab
2025-04-16  0:35 ` dpdklab
2025-04-16  0:44 ` dpdklab
2025-04-16  0:55 ` dpdklab
2025-04-16  1:06 ` |FAILURE| " dpdklab
2025-04-16  1:12 ` |PENDING| " dpdklab
2025-04-16  1:13 ` |SUCCESS| " dpdklab
2025-04-16  1:17 ` dpdklab
2025-04-16  1:32 ` |FAILURE| " dpdklab
2025-04-16  1:33 ` dpdklab
2025-04-16  1:43 ` |SUCCESS| " dpdklab
2025-04-16  2:20 ` dpdklab
2025-04-16  3:48 ` dpdklab
2025-04-16  6:34 ` dpdklab
2025-04-16  7:10 ` 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=67feee96.d40a0220.1a8ec0.2cdeSMTPIN_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).