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| pw142407-142409 [PATCH] [v4,3/3] dts: dynamic config test
Date: Mon, 15 Jul 2024 15:15:52 -0700 (PDT)	[thread overview]
Message-ID: <66959f98.050a0220.cb5c8.424fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240715160021.23352-3-dmarx@iol.unh.edu>

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

_Testing pending_

Submitter: Dean Marx <dmarx@iol.unh.edu>
Date: Monday, July 15 2024 16:00:21 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084

142407-142409 --> testing pending

Test environment and result as below:

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


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

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

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

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-15 22:16 UTC|newest]

Thread overview: 116+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240715160021.23352-3-dmarx@iol.unh.edu>
2024-07-15 15:33 ` |SUCCESS| pw142407-142409 [PATCH v4 3/3] dts: dynamic config test suite qemudev
2024-07-15 15:38 ` qemudev
2024-07-15 16:02 ` |SUCCESS| pw142409 " checkpatch
2024-07-15 17:44 ` 0-day Robot
2024-07-15 19:39 ` |SUCCESS| pw142407-142409 [PATCH] [v4,3/3] dts: dynamic config test dpdklab
2024-07-15 19:43 ` dpdklab
2024-07-15 19:46 ` dpdklab
2024-07-15 19:49 ` dpdklab
2024-07-15 19:56 ` dpdklab
2024-07-15 20:00 ` dpdklab
2024-07-15 20:01 ` dpdklab
2024-07-15 20:03 ` dpdklab
2024-07-15 21:39 ` |PENDING| " dpdklab
2024-07-15 21:46 ` |SUCCESS| " dpdklab
2024-07-15 21:55 ` |PENDING| " dpdklab
2024-07-15 21:55 ` dpdklab
2024-07-15 22:13 ` dpdklab
2024-07-15 22:15 ` dpdklab [this message]
2024-07-15 22:20 ` dpdklab
2024-07-15 22:20 ` dpdklab
2024-07-15 22:21 ` |SUCCESS| " dpdklab
2024-07-15 22:25 ` |PENDING| " dpdklab
2024-07-15 22:26 ` dpdklab
2024-07-15 22:29 ` dpdklab
2024-07-15 22:36 ` |SUCCESS| " dpdklab
2024-07-15 22:43 ` |PENDING| " dpdklab
2024-07-15 22:43 ` dpdklab
2024-07-15 22:44 ` dpdklab
2024-07-15 22:47 ` dpdklab
2024-07-15 22:50 ` dpdklab
2024-07-15 22:54 ` dpdklab
2024-07-15 22:58 ` dpdklab
2024-07-15 23:01 ` dpdklab
2024-07-15 23:03 ` dpdklab
2024-07-15 23:10 ` dpdklab
2024-07-15 23:11 ` dpdklab
2024-07-15 23:12 ` dpdklab
2024-07-15 23:17 ` dpdklab
2024-07-15 23:18 ` dpdklab
2024-07-15 23:18 ` dpdklab
2024-07-16  0:03 ` dpdklab
2024-07-16  0:23 ` dpdklab
2024-07-16  0:27 ` dpdklab
2024-07-16  0:29 ` dpdklab
2024-07-16  0:32 ` dpdklab
2024-07-16  0:34 ` dpdklab
2024-07-16  0:38 ` dpdklab
2024-07-16  0:39 ` dpdklab
2024-07-16  0:41 ` dpdklab
2024-07-16  0:42 ` dpdklab
2024-07-16  0:42 ` dpdklab
2024-07-16  0:44 ` dpdklab
2024-07-16  0:44 ` dpdklab
2024-07-16  0:45 ` dpdklab
2024-07-16  0:46 ` dpdklab
2024-07-16  0:46 ` dpdklab
2024-07-16  0:46 ` dpdklab
2024-07-16  0:46 ` dpdklab
2024-07-16  0:50 ` dpdklab
2024-07-16  0:50 ` dpdklab
2024-07-16  0:53 ` dpdklab
2024-07-16  0:56 ` dpdklab
2024-07-16  0:56 ` dpdklab
2024-07-16  1:03 ` dpdklab
2024-07-16  1:06 ` dpdklab
2024-07-16  1:14 ` dpdklab
2024-07-16  1:16 ` dpdklab
2024-07-16  1:17 ` dpdklab
2024-07-16  1:24 ` |SUCCESS| " dpdklab
2024-07-16  2:01 ` |PENDING| " dpdklab
2024-07-16  2:02 ` dpdklab
2024-07-16  2:17 ` dpdklab
2024-07-16  2:22 ` dpdklab
2024-07-16  2:22 ` dpdklab
2024-07-16  2:22 ` dpdklab
2024-07-16  2:23 ` dpdklab
2024-07-16  2:26 ` dpdklab
2024-07-16  2:27 ` dpdklab
2024-07-16  2:30 ` dpdklab
2024-07-16  2:31 ` dpdklab
2024-07-16  2:32 ` dpdklab
2024-07-16  2:34 ` dpdklab
2024-07-16  2:34 ` dpdklab
2024-07-16  2:37 ` dpdklab
2024-07-16  2:38 ` dpdklab
2024-07-16  2:39 ` dpdklab
2024-07-16  2:44 ` dpdklab
2024-07-16  2:44 ` dpdklab
2024-07-16  2:46 ` dpdklab
2024-07-16  2:48 ` |SUCCESS| " dpdklab
2024-07-16  2:50 ` |PENDING| " dpdklab
2024-07-16  2:53 ` dpdklab
2024-07-16  2:53 ` dpdklab
2024-07-16  2:54 ` dpdklab
2024-07-16  2:55 ` dpdklab
2024-07-16  2:56 ` dpdklab
2024-07-16  2:58 ` dpdklab
2024-07-16  2:58 ` dpdklab
2024-07-16  2:59 ` dpdklab
2024-07-16  2:59 ` dpdklab
2024-07-16  3:00 ` |SUCCESS| " dpdklab
2024-07-16  3:06 ` |PENDING| " dpdklab
2024-07-16  3:06 ` dpdklab
2024-07-16  3:07 ` dpdklab
2024-07-16  3:09 ` dpdklab
2024-07-16  3:10 ` dpdklab
2024-07-16  3:11 ` dpdklab
2024-07-16  3:19 ` |SUCCESS| " dpdklab
2024-07-16  3:23 ` |PENDING| " dpdklab
2024-07-16  3:28 ` |SUCCESS| " dpdklab
2024-07-16 11:55 ` dpdklab
2024-07-16 15:39 ` dpdklab
2024-07-16 15:44 ` dpdklab
2024-07-16 15:49 ` dpdklab
2024-07-16 15:54 ` dpdklab
2024-07-16 16:14 ` 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=66959f98.050a0220.cb5c8.424fSMTPIN_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).