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| pw140397-140399 [PATCH] [v3,3/3] dts: Improve logging for
Date: Wed, 29 May 2024 15:13:28 -0700 (PDT)	[thread overview]
Message-ID: <6657a888.050a0220.87004.b000SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240529194910.26803-4-jspewock@iol.unh.edu>

Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140399

_Testing PASS_

Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Wednesday, May 29 2024 19:49:10 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:76cef1af8bdaeaf67a5c4ca5df3f221df994dc46

140397-140399 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_compile_ovs |
+=====================+====================+======================+==================+
| FreeBSD 13.3        | PASS               | SKIPPED              | SKIPPED          |
+---------------------+--------------------+----------------------+------------------+
| Windows Server 2019 | PASS               | PASS                 | SKIPPED          |
+---------------------+--------------------+----------------------+------------------+
| FreeBSD 14.0        | PASS               | SKIPPED              | SKIPPED          |
+---------------------+--------------------+----------------------+------------------+
| Windows Server 2022 | PASS               | PASS                 | SKIPPED          |
+---------------------+--------------------+----------------------+------------------+
| CentOS Stream 8     | PASS               | SKIPPED              | PASS             |
+---------------------+--------------------+----------------------+------------------+
| CentOS Stream 9     | PASS               | SKIPPED              | PASS             |
+---------------------+--------------------+----------------------+------------------+


FreeBSD 13.3
	Kernel: 13.3-RELEASE-p1
	Compiler: clang 17.0.6

Windows Server 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

FreeBSD 14.0
	Kernel: 14.0
	Compiler: clang 16.0.6

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-29 22:13 UTC|newest]

Thread overview: 181+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240529194910.26803-4-jspewock@iol.unh.edu>
2024-05-29 19:23 ` |SUCCESS| pw140397-140399 [PATCH v3 3/3] dts: Improve logging for interactive shells qemudev
2024-05-29 19:27 ` qemudev
2024-05-29 19:50 ` |SUCCESS| pw140399 " checkpatch
2024-05-29 20:43 ` 0-day Robot
2024-05-29 21:01 ` |SUCCESS| pw140397-140399 [PATCH] [v3,3/3] dts: Improve logging for dpdklab
2024-05-29 21:04 ` dpdklab
2024-05-29 21:07 ` dpdklab
2024-05-29 21:08 ` dpdklab
2024-05-29 21:29 ` dpdklab
2024-05-29 21:36 ` dpdklab
2024-05-29 21:37 ` dpdklab
2024-05-29 21:49 ` dpdklab
2024-05-29 21:52 ` dpdklab
2024-05-29 21:53 ` dpdklab
2024-05-29 21:53 ` dpdklab
2024-05-29 21:55 ` dpdklab
2024-05-29 21:58 ` dpdklab
2024-05-29 21:58 ` dpdklab
2024-05-29 21:59 ` dpdklab
2024-05-29 22:00 ` dpdklab
2024-05-29 22:01 ` dpdklab
2024-05-29 22:01 ` dpdklab
2024-05-29 22:02 ` dpdklab
2024-05-29 22:02 ` dpdklab
2024-05-29 22:03 ` dpdklab
2024-05-29 22:04 ` dpdklab
2024-05-29 22:04 ` dpdklab
2024-05-29 22:04 ` dpdklab
2024-05-29 22:05 ` dpdklab
2024-05-29 22:06 ` dpdklab
2024-05-29 22:06 ` dpdklab
2024-05-29 22:08 ` dpdklab
2024-05-29 22:09 ` dpdklab
2024-05-29 22:10 ` dpdklab
2024-05-29 22:13 ` dpdklab
2024-05-29 22:13 ` dpdklab
2024-05-29 22:13 ` dpdklab [this message]
2024-05-29 22:13 ` dpdklab
2024-05-29 22:26 ` dpdklab
2024-05-29 22:32 ` dpdklab
2024-05-29 22:33 ` dpdklab
2024-05-29 22:35 ` dpdklab
2024-05-29 22:35 ` dpdklab
2024-05-29 22:37 ` dpdklab
2024-05-29 22:38 ` dpdklab
2024-05-29 22:39 ` dpdklab
2024-05-29 22:39 ` dpdklab
2024-05-29 22:40 ` dpdklab
2024-05-29 22:40 ` dpdklab
2024-05-29 22:41 ` dpdklab
2024-05-29 22:42 ` dpdklab
2024-05-29 22:43 ` dpdklab
2024-05-29 22:44 ` dpdklab
2024-05-29 22:44 ` dpdklab
2024-05-29 22:44 ` dpdklab
2024-05-29 22:44 ` dpdklab
2024-05-29 22:45 ` dpdklab
2024-05-29 22:45 ` dpdklab
2024-05-29 22:45 ` dpdklab
2024-05-29 22:46 ` dpdklab
2024-05-29 22:47 ` dpdklab
2024-05-29 22:47 ` dpdklab
2024-05-29 22:48 ` dpdklab
2024-05-29 23:14 ` dpdklab
2024-05-29 23:20 ` dpdklab
2024-05-29 23:21 ` dpdklab
2024-05-29 23:22 ` dpdklab
2024-05-29 23:23 ` dpdklab
2024-05-29 23:25 ` dpdklab
2024-05-29 23:26 ` dpdklab
2024-05-29 23:26 ` dpdklab
2024-05-29 23:26 ` dpdklab
2024-05-29 23:27 ` dpdklab
2024-05-29 23:31 ` dpdklab
2024-05-29 23:36 ` dpdklab
2024-05-29 23:38 ` dpdklab
2024-05-29 23:42 ` dpdklab
2024-05-29 23:42 ` dpdklab
2024-05-29 23:43 ` dpdklab
2024-05-30  6:52 ` dpdklab
2024-05-30  6:52 ` dpdklab
2024-05-30  6:53 ` dpdklab
2024-05-30 13:54 ` dpdklab
2024-05-30 13:54 ` dpdklab
2024-05-30 14:06 ` dpdklab
2024-06-01 13:45 ` dpdklab
2024-06-01 13:46 ` dpdklab
2024-06-01 13:48 ` dpdklab
2024-06-01 13:49 ` dpdklab
2024-06-01 13:50 ` dpdklab
2024-06-01 13:53 ` dpdklab
2024-06-01 13:55 ` dpdklab
2024-06-01 14:01 ` dpdklab
2024-06-01 15:50 ` dpdklab
2024-06-01 15:55 ` dpdklab
2024-06-01 15:56 ` dpdklab
2024-06-01 15:57 ` dpdklab
2024-06-01 15:57 ` dpdklab
2024-06-01 15:57 ` dpdklab
2024-06-01 16:00 ` dpdklab
2024-06-01 16:23 ` dpdklab
2024-06-01 16:33 ` dpdklab
2024-06-01 17:02 ` dpdklab
2024-06-01 17:04 ` dpdklab
2024-06-01 17:06 ` dpdklab
2024-06-01 17:10 ` dpdklab
2024-06-01 17:10 ` dpdklab
2024-06-01 17:16 ` dpdklab
2024-06-01 17:23 ` dpdklab
2024-06-01 17:30 ` dpdklab
2024-06-01 17:34 ` dpdklab
2024-06-01 17:45 ` dpdklab
2024-06-01 17:46 ` dpdklab
2024-06-01 17:47 ` dpdklab
2024-06-01 17:47 ` dpdklab
2024-06-01 17:48 ` dpdklab
2024-06-01 17:48 ` dpdklab
2024-06-01 17:49 ` dpdklab
2024-06-01 17:49 ` dpdklab
2024-06-01 17:50 ` dpdklab
2024-06-01 17:50 ` dpdklab
2024-06-01 17:51 ` dpdklab
2024-06-01 17:51 ` dpdklab
2024-06-01 17:52 ` dpdklab
2024-06-01 17:52 ` dpdklab
2024-06-01 17:52 ` dpdklab
2024-06-01 17:57 ` dpdklab
2024-06-01 17:57 ` dpdklab
2024-06-01 18:02 ` dpdklab
2024-06-01 18:05 ` dpdklab
2024-06-01 18:05 ` dpdklab
2024-06-01 18:06 ` dpdklab
2024-06-01 18:10 ` dpdklab
2024-06-01 18:14 ` dpdklab
2024-06-01 18:14 ` dpdklab
2024-06-01 18:15 ` dpdklab
2024-06-01 18:20 ` dpdklab
2024-06-01 18:21 ` dpdklab
2024-06-01 18:32 ` dpdklab
2024-06-01 18:39 ` dpdklab
2024-06-01 18:40 ` dpdklab
2024-06-01 18:41 ` dpdklab
2024-06-01 18:52 ` dpdklab
2024-06-01 18:53 ` dpdklab
2024-06-01 18:53 ` dpdklab
2024-06-01 18:53 ` dpdklab
2024-06-01 18:56 ` dpdklab
2024-06-01 18:57 ` dpdklab
2024-06-01 19:08 ` dpdklab
2024-06-01 19:09 ` dpdklab
2024-06-01 19:11 ` dpdklab
2024-06-01 19:14 ` dpdklab
2024-06-01 19:16 ` dpdklab
2024-06-01 19:18 ` dpdklab
2024-06-01 19:20 ` dpdklab
2024-06-01 19:20 ` dpdklab
2024-06-01 19:21 ` dpdklab
2024-06-01 19:23 ` dpdklab
2024-06-01 19:27 ` dpdklab
2024-06-01 19:30 ` dpdklab
2024-06-01 19:30 ` dpdklab
2024-06-01 19:34 ` dpdklab
2024-06-01 19:34 ` dpdklab
2024-06-01 19:38 ` dpdklab
2024-06-01 19:42 ` dpdklab
2024-06-01 19:43 ` dpdklab
2024-06-01 19:45 ` dpdklab
2024-06-01 19:46 ` dpdklab
2024-06-01 19:48 ` dpdklab
2024-06-01 19:55 ` dpdklab
2024-06-01 20:05 ` dpdklab
2024-06-01 20:23 ` dpdklab
2024-06-01 20:30 ` dpdklab
2024-06-01 20:39 ` dpdklab
2024-06-01 20:42 ` dpdklab
2024-06-01 20:46 ` dpdklab
2024-06-01 21:06 ` dpdklab
2024-06-01 21:10 ` dpdklab
2024-06-01 22:54 ` dpdklab
2024-06-01 23:07 ` dpdklab
2024-06-02  3:32 ` 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=6657a888.050a0220.87004.b000SMTPIN_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).