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| pw146077-146080 [PATCH] [v2,4/4] buildtools/chkincs: check
Date: Wed, 16 Oct 2024 17:40:51 -0700 (PDT)	[thread overview]
Message-ID: <67105d13.050a0220.3c6cce.ce29SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241016113817.3956187-5-david.marchand@redhat.com>

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

_Testing PASS_

Submitter: David Marchand <david.marchand@redhat.com>
Date: Wednesday, October 16 2024 11:38:16 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cc8764c6c9af150131f714bbe8d39de861d5e377

146077-146080 --> testing pass

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

Test environment and result as below:

+---------------------+-----------------------+----------------------+--------------------+
|     Environment     | dpdk_win_llvm_compile | dpdk_mingw64_compile | dpdk_meson_compile |
+=====================+=======================+======================+====================+
| Windows Server 2022 | PASS                  | PASS                 | SKIPPED            |
+---------------------+-----------------------+----------------------+--------------------+
| FreeBSD 13.4        | SKIPPED               | SKIPPED              | PASS               |
+---------------------+-----------------------+----------------------+--------------------+
| FreeBSD 14.1        | SKIPPED               | SKIPPED              | PASS               |
+---------------------+-----------------------+----------------------+--------------------+


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

FreeBSD 13.4
	Kernel: 13.4-RELEASE-p1
	Compiler: clang 18.1.6

FreeBSD 14.1
	Kernel: 14.1-RELEASE-p3
	Compiler: clang 18.1.5

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-10-17  0:40 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241016113817.3956187-5-david.marchand@redhat.com>
2024-10-16 11:13 ` |SUCCESS| pw146077-146080 [PATCH v2 4/4] buildtools/chkincs: check headers with stable API only qemudev
2024-10-16 11:18 ` qemudev
2024-10-16 11:39 ` |SUCCESS| pw146080 " checkpatch
2024-10-16 12:42 ` 0-day Robot
2024-10-16 13:08 ` |SUCCESS| pw146077-146080 [PATCH] [v2,4/4] buildtools/chkincs: check dpdklab
2024-10-16 13:09 ` dpdklab
2024-10-16 13:14 ` dpdklab
2024-10-16 13:17 ` dpdklab
2024-10-16 13:21 ` dpdklab
2024-10-16 13:26 ` dpdklab
2024-10-16 14:43 ` dpdklab
2024-10-16 16:03 ` dpdklab
2024-10-16 16:56 ` dpdklab
2024-10-16 18:45 ` dpdklab
2024-10-17  0:40 ` dpdklab [this message]
2024-10-17  0:41 ` dpdklab
2024-10-17  0:54 ` |PENDING| " dpdklab
2024-10-17  1:36 ` dpdklab
2024-10-17  3:31 ` |SUCCESS| " dpdklab
2024-10-17  4:47 ` |WARNING| " dpdklab
2024-10-17  7:20 ` |PENDING| " dpdklab
2024-10-17  8:24 ` |WARNING| " dpdklab
2024-10-17 11:35 ` dpdklab
2024-10-17 11:36 ` |SUCCESS| " dpdklab
2024-10-17 16:11 ` dpdklab
2024-10-19 16:30 ` 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=67105d13.050a0220.3c6cce.ce29SMTPIN_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).