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: |PENDING| pw144131 [PATCH] [v2] devtools: fix false positive from ch
Date: Tue, 17 Sep 2024 19:05:17 -0700 (PDT)	[thread overview]
Message-ID: <66ea355d.050a0220.1cdf0.22f1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240917165611.9943-1-stephen@networkplumber.org>

Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/144131

_Testing pending_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, September 17 2024 16:56:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

144131 --> testing pending

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

Test environment and result as below:

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


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.3
	Kernel: 13.3-RELEASE-p5
	Compiler: clang 17.0.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/31051/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-09-18  2:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240917165611.9943-1-stephen@networkplumber.org>
2024-09-17 16:29 ` |SUCCESS| pw144131 [PATCH v2] devtools: fix false positive from checkpatch qemudev
2024-09-17 16:33 ` qemudev
2024-09-17 16:57 ` |WARNING| " checkpatch
2024-09-17 17:44 ` |SUCCESS| " 0-day Robot
2024-09-17 22:02 ` |SUCCESS| pw144131 [PATCH] [v2] devtools: fix false positive from ch dpdklab
2024-09-18  0:03 ` dpdklab
2024-09-18  0:04 ` dpdklab
2024-09-18  0:27 ` dpdklab
2024-09-18  0:40 ` dpdklab
2024-09-18  2:05 ` dpdklab [this message]
2024-09-18  2:22 ` dpdklab
2024-09-18  2:31 ` |PENDING| " dpdklab
2024-09-18  3:18 ` |SUCCESS| " dpdklab
2024-09-18  3:26 ` |PENDING| " dpdklab
2024-09-18  4:13 ` |SUCCESS| " dpdklab
2024-09-18  4:14 ` dpdklab
2024-09-18  4:50 ` dpdklab
2024-09-18  5:06 ` dpdklab
2024-09-18  5:07 ` dpdklab
2024-09-18  5:09 ` dpdklab
2024-09-18  6:08 ` dpdklab
2024-09-18 10:24 ` dpdklab
2024-09-18 12:35 ` dpdklab
2024-09-22  9:52 ` dpdklab
2024-09-22 10:05 ` 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=66ea355d.050a0220.1cdf0.22f1SMTPIN_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).