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| pw142718 [PATCH] eventdev: do not use zero length arrays
Date: Thu, 25 Jul 2024 22:42:50 -0700 (PDT)	[thread overview]
Message-ID: <66a3375a.050a0220.3b144f.a559SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240725171609.142344-1-stephen@networkplumber.org>

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

_Testing pending_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thursday, July 25 2024 17:15:27 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084

142718 --> testing pending

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

Test environment and result as below:

+---------------------+--------------------+----------------------+-------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_msvc_compile |
+=====================+====================+======================+===================+
| Windows Server 2019 | PEND               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2022 | PEND               | PASS                 | PEND              |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 13.3        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 14.1        | PASS               | SKIPPED              | 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/30620/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-26  5:42 UTC|newest]

Thread overview: 117+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240725171609.142344-1-stephen@networkplumber.org>
2024-07-25 16:51 ` |SUCCESS| " qemudev
2024-07-25 16:56 ` qemudev
2024-07-25 17:19 ` checkpatch
2024-07-25 18:23 ` 0-day Robot
2024-07-26  3:45 ` dpdklab
2024-07-26  4:11 ` dpdklab
2024-07-26  4:11 ` dpdklab
2024-07-26  4:17 ` dpdklab
2024-07-26  4:18 ` dpdklab
2024-07-26  4:24 ` dpdklab
2024-07-26  4:29 ` |PENDING| " dpdklab
2024-07-26  4:30 ` |SUCCESS| " dpdklab
2024-07-26  4:32 ` dpdklab
2024-07-26  4:36 ` |PENDING| " dpdklab
2024-07-26  4:41 ` dpdklab
2024-07-26  4:43 ` dpdklab
2024-07-26  4:45 ` |SUCCESS| " dpdklab
2024-07-26  4:46 ` |PENDING| " dpdklab
2024-07-26  4:47 ` dpdklab
2024-07-26  4:50 ` dpdklab
2024-07-26  4:54 ` |SUCCESS| " dpdklab
2024-07-26  4:56 ` |PENDING| " dpdklab
2024-07-26  4:56 ` dpdklab
2024-07-26  4:57 ` dpdklab
2024-07-26  4:58 ` dpdklab
2024-07-26  5:05 ` dpdklab
2024-07-26  5:05 ` dpdklab
2024-07-26  5:06 ` dpdklab
2024-07-26  5:08 ` dpdklab
2024-07-26  5:09 ` |SUCCESS| " dpdklab
2024-07-26  5:10 ` |PENDING| " dpdklab
2024-07-26  5:28 ` |SUCCESS| " dpdklab
2024-07-26  5:36 ` |PENDING| " dpdklab
2024-07-26  5:39 ` |SUCCESS| " dpdklab
2024-07-26  5:41 ` |PENDING| " dpdklab
2024-07-26  5:42 ` dpdklab [this message]
2024-07-26  5:45 ` dpdklab
2024-07-26  5:46 ` dpdklab
2024-07-26  5:53 ` |SUCCESS| " dpdklab
2024-07-26  5:56 ` |PENDING| " dpdklab
2024-07-26  6:06 ` dpdklab
2024-07-26  6:10 ` |SUCCESS| " dpdklab
2024-07-26  6:14 ` dpdklab
2024-07-26  6:33 ` |PENDING| " dpdklab
2024-07-26  6:34 ` |SUCCESS| " dpdklab
2024-07-26  6:35 ` |PENDING| " dpdklab
2024-07-26  6:38 ` dpdklab
2024-07-26  6:42 ` dpdklab
2024-07-26  6:49 ` dpdklab
2024-07-26  6:51 ` dpdklab
2024-07-26  6:51 ` dpdklab
2024-07-26  6:57 ` dpdklab
2024-07-26  7:01 ` dpdklab
2024-07-26  7:02 ` dpdklab
2024-07-26  7:06 ` dpdklab
2024-07-26  7:06 ` dpdklab
2024-07-26  7:07 ` dpdklab
2024-07-26  7:09 ` dpdklab
2024-07-26  7:10 ` dpdklab
2024-07-26  7:10 ` dpdklab
2024-07-26  7:11 ` dpdklab
2024-07-26  7:11 ` dpdklab
2024-07-26  7:11 ` dpdklab
2024-07-26  7:12 ` dpdklab
2024-07-26  7:12 ` dpdklab
2024-07-26  7:15 ` dpdklab
2024-07-26  7:15 ` dpdklab
2024-07-26  7:15 ` dpdklab
2024-07-26  7:17 ` dpdklab
2024-07-26  7:20 ` dpdklab
2024-07-26  7:22 ` dpdklab
2024-07-26  7:22 ` dpdklab
2024-07-26  7:24 ` dpdklab
2024-07-26  7:25 ` dpdklab
2024-07-26  7:25 ` dpdklab
2024-07-26  7:26 ` dpdklab
2024-07-26  7:26 ` dpdklab
2024-07-26  7:29 ` dpdklab
2024-07-26  7:30 ` dpdklab
2024-07-26  7:31 ` dpdklab
2024-07-26  7:31 ` dpdklab
2024-07-26  7:31 ` dpdklab
2024-07-26  7:31 ` dpdklab
2024-07-26  7:32 ` dpdklab
2024-07-26  7:32 ` dpdklab
2024-07-26  7:33 ` dpdklab
2024-07-26  7:34 ` dpdklab
2024-07-26  7:34 ` dpdklab
2024-07-26  7:35 ` dpdklab
2024-07-26  7:35 ` dpdklab
2024-07-26  7:35 ` dpdklab
2024-07-26  7:36 ` dpdklab
2024-07-26  7:36 ` dpdklab
2024-07-26  7:37 ` dpdklab
2024-07-26  7:39 ` dpdklab
2024-07-26  7:40 ` dpdklab
2024-07-26  7:42 ` dpdklab
2024-07-26  7:43 ` dpdklab
2024-07-26  7:43 ` dpdklab
2024-07-26  7:44 ` dpdklab
2024-07-26  7:46 ` dpdklab
2024-07-26  7:48 ` dpdklab
2024-07-26  7:50 ` dpdklab
2024-07-26  7:50 ` dpdklab
2024-07-26  7:53 ` dpdklab
2024-07-26  7:53 ` dpdklab
2024-07-26  7:56 ` |SUCCESS| " dpdklab
2024-07-26  7:56 ` dpdklab
2024-07-26  7:56 ` dpdklab
2024-07-26  7:57 ` |PENDING| " dpdklab
2024-07-26  7:57 ` dpdklab
2024-07-26  8:04 ` dpdklab
2024-07-26  8:08 ` dpdklab
2024-07-26  8:17 ` dpdklab
2024-07-26  8:22 ` dpdklab
2024-07-26  8:29 ` |SUCCESS| " dpdklab
2024-07-26 16:49 ` 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=66a3375a.050a0220.3b144f.a559SMTPIN_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).