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| pw142959-142963 [PATCH] [v15,5/5] dts: add API doc generat
Date: Tue, 06 Aug 2024 14:39:03 -0700 (PDT)	[thread overview]
Message-ID: <66b297f7.170a0220.eece2.ae9cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240806151937.391917-6-juraj.linkes@pantheon.tech>

Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/142963

_Testing PASS_

Submitter: Juraj Linkes <juraj.linkes@pantheon.tech>
Date: Tuesday, August 06 2024 15:19:37 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b3485f4293997d35b6daecc3437bb0c183a51fb3

142959-142963 --> testing pass

Upstream job id: Windows-Compile-DPDK-Mingw64#21325

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+
| FreeBSD 13.3        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| FreeBSD 14.1        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+


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

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

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

FreeBSD 14.1
	Kernel: 14.1
	Compiler: clang 18.1.5

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-08-06 21:39 UTC|newest]

Thread overview: 115+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240806151937.391917-6-juraj.linkes@pantheon.tech>
2024-08-06 15:07 ` |SUCCESS| pw142959-142963 [PATCH v15 5/5] dts: add API doc generation qemudev
2024-08-06 15:12 ` qemudev
2024-08-06 15:21 ` |WARNING| pw142963 " checkpatch
2024-08-06 16:23 ` |SUCCESS| " 0-day Robot
2024-08-06 19:32 ` |SUCCESS| pw142959-142963 [PATCH] [v15,5/5] dts: add API doc generat dpdklab
2024-08-06 19:33 ` |PENDING| " dpdklab
2024-08-06 19:38 ` dpdklab
2024-08-06 19:47 ` |SUCCESS| " dpdklab
2024-08-06 19:51 ` dpdklab
2024-08-06 20:09 ` dpdklab
2024-08-06 20:18 ` |PENDING| " dpdklab
2024-08-06 20:26 ` |SUCCESS| " dpdklab
2024-08-06 21:02 ` dpdklab
2024-08-06 21:04 ` dpdklab
2024-08-06 21:24 ` |PENDING| " dpdklab
2024-08-06 21:26 ` dpdklab
2024-08-06 21:26 ` dpdklab
2024-08-06 21:27 ` dpdklab
2024-08-06 21:32 ` dpdklab
2024-08-06 21:33 ` |SUCCESS| " dpdklab
2024-08-06 21:34 ` |PENDING| " dpdklab
2024-08-06 21:36 ` dpdklab
2024-08-06 21:39 ` dpdklab [this message]
2024-08-06 21:39 ` dpdklab
2024-08-06 21:47 ` dpdklab
2024-08-06 21:48 ` |SUCCESS| " dpdklab
2024-08-06 21:48 ` |PENDING| " dpdklab
2024-08-06 21:52 ` dpdklab
2024-08-06 21:52 ` dpdklab
2024-08-06 21:53 ` dpdklab
2024-08-06 21:54 ` dpdklab
2024-08-06 21:54 ` dpdklab
2024-08-06 21:55 ` dpdklab
2024-08-06 21:57 ` dpdklab
2024-08-06 21:58 ` dpdklab
2024-08-06 21:59 ` dpdklab
2024-08-06 22:00 ` dpdklab
2024-08-06 22:02 ` |SUCCESS| " dpdklab
2024-08-06 22:03 ` |PENDING| " dpdklab
2024-08-06 22:03 ` dpdklab
2024-08-06 22:05 ` dpdklab
2024-08-06 22:07 ` |SUCCESS| " dpdklab
2024-08-06 22:07 ` |PENDING| " dpdklab
2024-08-06 22:13 ` dpdklab
2024-08-06 22:14 ` dpdklab
2024-08-06 22:18 ` dpdklab
2024-08-06 22:19 ` dpdklab
2024-08-06 22:22 ` dpdklab
2024-08-06 22:24 ` dpdklab
2024-08-06 22:26 ` |SUCCESS| " dpdklab
2024-08-06 22:27 ` |PENDING| " dpdklab
2024-08-06 22:29 ` dpdklab
2024-08-06 22:29 ` dpdklab
2024-08-06 22:31 ` dpdklab
2024-08-06 22:32 ` dpdklab
2024-08-06 22:33 ` dpdklab
2024-08-06 22:36 ` dpdklab
2024-08-06 22:38 ` |SUCCESS| " dpdklab
2024-08-06 22:39 ` |PENDING| " dpdklab
2024-08-06 22:39 ` dpdklab
2024-08-06 22:40 ` dpdklab
2024-08-06 22:42 ` dpdklab
2024-08-06 22:43 ` dpdklab
2024-08-06 22:46 ` dpdklab
2024-08-06 22:47 ` dpdklab
2024-08-06 22:48 ` dpdklab
2024-08-06 22:48 ` dpdklab
2024-08-06 22:49 ` dpdklab
2024-08-06 22:53 ` dpdklab
2024-08-06 22:54 ` dpdklab
2024-08-06 22:55 ` dpdklab
2024-08-06 22:56 ` dpdklab
2024-08-06 23:02 ` dpdklab
2024-08-06 23:03 ` |SUCCESS| " dpdklab
2024-08-06 23:05 ` |PENDING| " dpdklab
2024-08-06 23:06 ` dpdklab
2024-08-06 23:07 ` dpdklab
2024-08-06 23:08 ` dpdklab
2024-08-06 23:10 ` dpdklab
2024-08-06 23:11 ` dpdklab
2024-08-06 23:11 ` dpdklab
2024-08-06 23:11 ` dpdklab
2024-08-06 23:13 ` dpdklab
2024-08-06 23:17 ` dpdklab
2024-08-06 23:18 ` dpdklab
2024-08-06 23:20 ` dpdklab
2024-08-06 23:20 ` dpdklab
2024-08-06 23:21 ` dpdklab
2024-08-06 23:21 ` dpdklab
2024-08-06 23:22 ` dpdklab
2024-08-06 23:22 ` dpdklab
2024-08-06 23:24 ` dpdklab
2024-08-06 23:26 ` dpdklab
2024-08-06 23:27 ` dpdklab
2024-08-06 23:27 ` dpdklab
2024-08-06 23:28 ` dpdklab
2024-08-06 23:28 ` dpdklab
2024-08-06 23:28 ` dpdklab
2024-08-06 23:28 ` dpdklab
2024-08-06 23:29 ` dpdklab
2024-08-06 23:29 ` dpdklab
2024-08-06 23:31 ` dpdklab
2024-08-06 23:31 ` dpdklab
2024-08-06 23:32 ` dpdklab
2024-08-06 23:32 ` |SUCCESS| " dpdklab
2024-08-06 23:36 ` |PENDING| " dpdklab
2024-08-06 23:43 ` dpdklab
2024-08-06 23:44 ` dpdklab
2024-08-06 23:46 ` |SUCCESS| " dpdklab
2024-08-06 23:49 ` |PENDING| " dpdklab
2024-08-06 23:56 ` |SUCCESS| " dpdklab
2024-08-07  1:44 ` dpdklab
2024-08-07  8:20 ` dpdklab
2024-08-07  8:29 ` dpdklab
2024-08-07  8:43 ` 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=66b297f7.170a0220.eece2.ae9cSMTPIN_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).