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| pw141446-141448 [PATCH] [v4,3/3] dts: Improve logging for
Date: Thu, 20 Jun 2024 20:30:35 -0700 (PDT)	[thread overview]
Message-ID: <6674f3db.170a0220.a3746.380cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240620173609.15375-4-jspewock@iol.unh.edu>

Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/141448

_Testing PASS_

Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Thursday, June 20 2024 17:36:09 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:4a44d97f0a52a76258c6a6cb6a713f4380a8ab1f

141446-141448 --> testing pass

Test environment and result as below:

+-----------------------------+----------------+--------------+
|         Environment         | dpdk_unit_test | lpm_autotest |
+=============================+================+==============+
| 32-bit Ubuntu 20.04.4 (ARM) | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| CentOS Stream 9 (ARM)       | PASS           | SKIPPED      |
+-----------------------------+----------------+--------------+
| Ubuntu 20.04 ARM SVE        | SKIPPED        | PASS         |
+-----------------------------+----------------+--------------+


32-bit Ubuntu 20.04.4 (ARM)
	Kernel: 5.4.0-155-generic aarch64
	Compiler: gcc 9.4

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.4.1

Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-167-generic
	Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-21  3:30 UTC|newest]

Thread overview: 129+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240620173609.15375-4-jspewock@iol.unh.edu>
2024-06-20 17:10 ` |SUCCESS| pw141446-141448 [PATCH v4 3/3] dts: Improve logging for interactive shells qemudev
2024-06-20 17:14 ` qemudev
2024-06-20 17:37 ` |SUCCESS| pw141448 " checkpatch
2024-06-20 18:25 ` 0-day Robot
2024-06-20 21:34 ` |SUCCESS| pw141446-141448 [PATCH] [v4,3/3] dts: Improve logging for dpdklab
2024-06-20 21:36 ` dpdklab
2024-06-20 21:37 ` dpdklab
2024-06-20 21:41 ` |FAILURE| " dpdklab
2024-06-20 21:43 ` |SUCCESS| " dpdklab
2024-06-20 22:09 ` |FAILURE| " dpdklab
2024-06-20 22:13 ` |SUCCESS| " dpdklab
2024-06-20 22:14 ` dpdklab
2024-06-20 22:22 ` dpdklab
2024-06-20 22:23 ` dpdklab
2024-06-20 22:32 ` dpdklab
2024-06-20 22:38 ` dpdklab
2024-06-20 22:44 ` dpdklab
2024-06-20 22:58 ` |FAILURE| " dpdklab
2024-06-20 23:13 ` dpdklab
2024-06-20 23:14 ` dpdklab
2024-06-20 23:15 ` |SUCCESS| " dpdklab
2024-06-20 23:45 ` dpdklab
2024-06-21  0:02 ` dpdklab
2024-06-21  0:03 ` dpdklab
2024-06-21  0:05 ` dpdklab
2024-06-21  0:10 ` dpdklab
2024-06-21  0:10 ` dpdklab
2024-06-21  0:17 ` dpdklab
2024-06-21  0:18 ` dpdklab
2024-06-21  0:32 ` dpdklab
2024-06-21  0:34 ` dpdklab
2024-06-21  0:34 ` dpdklab
2024-06-21  0:34 ` dpdklab
2024-06-21  0:37 ` dpdklab
2024-06-21  0:38 ` dpdklab
2024-06-21  0:39 ` dpdklab
2024-06-21  0:42 ` dpdklab
2024-06-21  0:44 ` dpdklab
2024-06-21  0:45 ` dpdklab
2024-06-21  0:46 ` dpdklab
2024-06-21  0:46 ` dpdklab
2024-06-21  0:48 ` dpdklab
2024-06-21  0:51 ` dpdklab
2024-06-21  2:45 ` dpdklab
2024-06-21  2:48 ` dpdklab
2024-06-21  2:48 ` dpdklab
2024-06-21  2:49 ` dpdklab
2024-06-21  2:50 ` dpdklab
2024-06-21  2:51 ` dpdklab
2024-06-21  2:52 ` dpdklab
2024-06-21  2:52 ` dpdklab
2024-06-21  2:53 ` dpdklab
2024-06-21  2:54 ` dpdklab
2024-06-21  3:07 ` dpdklab
2024-06-21  3:10 ` dpdklab
2024-06-21  3:12 ` dpdklab
2024-06-21  3:16 ` dpdklab
2024-06-21  3:17 ` dpdklab
2024-06-21  3:18 ` dpdklab
2024-06-21  3:21 ` dpdklab
2024-06-21  3:23 ` dpdklab
2024-06-21  3:23 ` dpdklab
2024-06-21  3:25 ` dpdklab
2024-06-21  3:26 ` dpdklab
2024-06-21  3:27 ` dpdklab
2024-06-21  3:29 ` dpdklab
2024-06-21  3:30 ` dpdklab
2024-06-21  3:30 ` dpdklab [this message]
2024-06-21  3:31 ` dpdklab
2024-06-21  3:32 ` dpdklab
2024-06-21  3:35 ` dpdklab
2024-06-21  3:44 ` dpdklab
2024-06-21  3:50 ` dpdklab
2024-06-21  3:50 ` dpdklab
2024-06-21  3:50 ` dpdklab
2024-06-21  3:51 ` dpdklab
2024-06-21  3:52 ` dpdklab
2024-06-21  3:53 ` dpdklab
2024-06-21  3:53 ` dpdklab
2024-06-21  3:54 ` dpdklab
2024-06-21  3:55 ` dpdklab
2024-06-21  3:56 ` dpdklab
2024-06-21  3:56 ` dpdklab
2024-06-21  3:58 ` dpdklab
2024-06-21  3:58 ` dpdklab
2024-06-21  3:59 ` dpdklab
2024-06-21  3:59 ` dpdklab
2024-06-21  4:01 ` dpdklab
2024-06-21  4:02 ` dpdklab
2024-06-21  4:07 ` dpdklab
2024-06-21  4:08 ` dpdklab
2024-06-21  4:08 ` dpdklab
2024-06-21  4:10 ` dpdklab
2024-06-21  4:20 ` dpdklab
2024-06-21  4:35 ` dpdklab
2024-06-21  4:39 ` dpdklab
2024-06-21  4:39 ` dpdklab
2024-06-21  4:41 ` dpdklab
2024-06-21  4:41 ` dpdklab
2024-06-21  4:42 ` dpdklab
2024-06-21  4:43 ` dpdklab
2024-06-21  4:43 ` dpdklab
2024-06-21  4:44 ` dpdklab
2024-06-21  4:45 ` dpdklab
2024-06-21  4:49 ` dpdklab
2024-06-21  4:52 ` dpdklab
2024-06-21  4:56 ` dpdklab
2024-06-21  5:20 ` dpdklab
2024-06-21  5:22 ` dpdklab
2024-06-21  5:26 ` dpdklab
2024-06-21 15:51 ` dpdklab
2024-06-21 15:52 ` dpdklab
2024-06-21 15:53 ` dpdklab
2024-06-21 15:55 ` dpdklab
2024-06-21 15:58 ` |FAILURE| " dpdklab
2024-06-21 15:59 ` |SUCCESS| " dpdklab
2024-06-21 15:59 ` dpdklab
2024-06-21 16:00 ` |FAILURE| " dpdklab
2024-06-21 16:08 ` |SUCCESS| " dpdklab
2024-06-21 16:08 ` |FAILURE| " dpdklab
2024-06-21 16:11 ` |SUCCESS| " dpdklab
2024-06-21 16:11 ` dpdklab
2024-06-21 16:15 ` dpdklab
2024-06-21 16:19 ` dpdklab
2024-06-21 16:21 ` dpdklab
2024-06-21 16:22 ` dpdklab
2024-06-21 16:24 ` dpdklab
2024-06-21 16:37 ` dpdklab
2024-06-22  8:45 ` 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=6674f3db.170a0220.a3746.380cSMTPIN_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).