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| pw142819 [PATCH] buildtools/cmdline: fix meson error when
Date: Fri, 02 Aug 2024 00:02:50 -0700 (PDT)	[thread overview]
Message-ID: <66ac849a.050a0220.1ae00a.44ffSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240801100153.41779-2-rjarry@redhat.com>

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

_Testing PASS_

Submitter: Robin Jarry <rjarry@redhat.com>
Date: Thursday, August 01 2024 10:01:54 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b3485f4293997d35b6daecc3437bb0c183a51fb3

142819 --> testing pass

Upstream job id: Generic-VM-DPDK-Compile-Meson#28465

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/30694/

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-02  7:02 UTC|newest]

Thread overview: 113+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240801100153.41779-2-rjarry@redhat.com>
2024-08-01  9:35 ` |SUCCESS| pw142819 [PATCH dpdk] buildtools/cmdline: fix meson error when used as a subproject qemudev
2024-08-01  9:39 ` qemudev
2024-08-01 10:03 ` checkpatch
2024-08-01 13:42 ` 0-day Robot
2024-08-02  3:24 ` |SUCCESS| pw142819 [PATCH] buildtools/cmdline: fix meson error when dpdklab
2024-08-02  3:28 ` |PENDING| " dpdklab
2024-08-02  3:33 ` dpdklab
2024-08-02  3:42 ` |SUCCESS| " dpdklab
2024-08-02  3:46 ` dpdklab
2024-08-02  3:55 ` dpdklab
2024-08-02  4:34 ` |PENDING| " dpdklab
2024-08-02  4:42 ` |SUCCESS| " dpdklab
2024-08-02  5:00 ` |PENDING| " dpdklab
2024-08-02  5:10 ` dpdklab
2024-08-02  5:14 ` dpdklab
2024-08-02  5:16 ` |SUCCESS| " dpdklab
2024-08-02  5:18 ` |PENDING| " dpdklab
2024-08-02  5:22 ` dpdklab
2024-08-02  5:30 ` dpdklab
2024-08-02  5:31 ` dpdklab
2024-08-02  5:34 ` dpdklab
2024-08-02  5:35 ` dpdklab
2024-08-02  5:40 ` dpdklab
2024-08-02  5:41 ` dpdklab
2024-08-02  5:41 ` dpdklab
2024-08-02  5:44 ` |SUCCESS| " dpdklab
2024-08-02  5:44 ` dpdklab
2024-08-02  5:59 ` dpdklab
2024-08-02  6:03 ` dpdklab
2024-08-02  6:08 ` dpdklab
2024-08-02  6:28 ` dpdklab
2024-08-02  6:33 ` dpdklab
2024-08-02  6:52 ` |PENDING| " dpdklab
2024-08-02  6:54 ` dpdklab
2024-08-02  6:55 ` dpdklab
2024-08-02  6:58 ` dpdklab
2024-08-02  6:59 ` dpdklab
2024-08-02  7:01 ` dpdklab
2024-08-02  7:02 ` |SUCCESS| " dpdklab
2024-08-02  7:02 ` dpdklab [this message]
2024-08-02  7:08 ` |PENDING| " dpdklab
2024-08-02  7:10 ` dpdklab
2024-08-02  7:10 ` dpdklab
2024-08-02  7:10 ` dpdklab
2024-08-02  7:11 ` dpdklab
2024-08-02  7:13 ` dpdklab
2024-08-02  7:13 ` |SUCCESS| " dpdklab
2024-08-02  7:15 ` |PENDING| " dpdklab
2024-08-02  7:17 ` dpdklab
2024-08-02  7:19 ` dpdklab
2024-08-02  7:19 ` dpdklab
2024-08-02  7:22 ` dpdklab
2024-08-02  7:22 ` dpdklab
2024-08-02  7:22 ` dpdklab
2024-08-02  7:25 ` dpdklab
2024-08-02  7:27 ` dpdklab
2024-08-02  7:31 ` dpdklab
2024-08-02  7:31 ` dpdklab
2024-08-02  7:31 ` dpdklab
2024-08-02  7:31 ` dpdklab
2024-08-02  7:35 ` dpdklab
2024-08-02  7:37 ` dpdklab
2024-08-02  7:38 ` dpdklab
2024-08-02  7:39 ` dpdklab
2024-08-02  7:40 ` dpdklab
2024-08-02  7:40 ` dpdklab
2024-08-02  7:42 ` dpdklab
2024-08-02  7:42 ` dpdklab
2024-08-02  7:43 ` dpdklab
2024-08-02  7:45 ` dpdklab
2024-08-02  7:45 ` |SUCCESS| " dpdklab
2024-08-02  7:46 ` dpdklab
2024-08-02  7:46 ` |PENDING| " dpdklab
2024-08-02  7:46 ` |SUCCESS| " dpdklab
2024-08-02  7:51 ` dpdklab
2024-08-02  7:51 ` |PENDING| " dpdklab
2024-08-02  7:54 ` dpdklab
2024-08-02  7:56 ` dpdklab
2024-08-02  7:59 ` dpdklab
2024-08-02  7:59 ` dpdklab
2024-08-02  8:00 ` dpdklab
2024-08-02  8:01 ` dpdklab
2024-08-02  8:01 ` dpdklab
2024-08-02  8:02 ` dpdklab
2024-08-02  8:03 ` dpdklab
2024-08-02  8:04 ` dpdklab
2024-08-02  8:04 ` dpdklab
2024-08-02  8:05 ` dpdklab
2024-08-02  8:05 ` dpdklab
2024-08-02  8:06 ` dpdklab
2024-08-02  8:06 ` dpdklab
2024-08-02  8:13 ` dpdklab
2024-08-02  8:16 ` dpdklab
2024-08-02  8:16 ` dpdklab
2024-08-02  8:17 ` dpdklab
2024-08-02  8:18 ` dpdklab
2024-08-02  8:18 ` dpdklab
2024-08-02  8:19 ` dpdklab
2024-08-02  8:19 ` dpdklab
2024-08-02  8:21 ` dpdklab
2024-08-02  8:23 ` dpdklab
2024-08-02  8:23 ` dpdklab
2024-08-02  8:24 ` dpdklab
2024-08-02  8:29 ` dpdklab
2024-08-02  8:31 ` dpdklab
2024-08-02  8:38 ` |SUCCESS| " dpdklab
2024-08-02  9:04 ` |PENDING| " dpdklab
2024-08-02  9:20 ` dpdklab
2024-08-02  9:27 ` |SUCCESS| " dpdklab
2024-08-03  6:11 ` dpdklab
2024-08-06  8:01 ` dpdklab
2024-08-06  8:09 ` dpdklab
2024-08-06  8:24 ` 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=66ac849a.050a0220.1ae00a.44ffSMTPIN_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).