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| pw142776 [PATCH] [1/1] ml/cnxk: enable data caching for al
Date: Wed, 31 Jul 2024 08:18:43 -0700 (PDT)	[thread overview]
Message-ID: <66aa55d3.050a0220.2f0a92.c56bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240731060652.7937-1-syalavarthi@marvell.com>

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

_Testing pending_

Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Wednesday, July 31 2024 06:06:52 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:781d698ae2acb9bc7eed06f447cb8355673f7d81

142776 --> testing pending

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

Test environment and result as below:

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


FreeBSD 13.3
	Kernel: 13.3-RELEASE-p1
	Compiler: clang 17.0.6

FreeBSD 14.1
	Kernel: 14.1
	Compiler: clang 18.1.5

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

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

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-31 15:20 UTC|newest]

Thread overview: 113+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240731060652.7937-1-syalavarthi@marvell.com>
2024-07-31  6:04 ` |SUCCESS| pw142776 [PATCH 1/1] ml/cnxk: enable data caching for all MRVL layers qemudev
2024-07-31  6:08 ` qemudev
2024-07-31  6:15 ` checkpatch
2024-07-31  7:02 ` 0-day Robot
2024-07-31 11:04 ` |SUCCESS| pw142776 [PATCH] [1/1] ml/cnxk: enable data caching for al dpdklab
2024-07-31 11:19 ` |PENDING| " dpdklab
2024-07-31 11:29 ` dpdklab
2024-07-31 11:32 ` |SUCCESS| " dpdklab
2024-07-31 11:38 ` dpdklab
2024-07-31 11:42 ` dpdklab
2024-07-31 11:46 ` dpdklab
2024-07-31 11:55 ` |PENDING| " dpdklab
2024-07-31 11:59 ` |SUCCESS| " dpdklab
2024-07-31 12:05 ` |PENDING| " dpdklab
2024-07-31 12:06 ` dpdklab
2024-07-31 12:07 ` dpdklab
2024-07-31 12:09 ` dpdklab
2024-07-31 12:10 ` dpdklab
2024-07-31 12:12 ` dpdklab
2024-07-31 12:13 ` |SUCCESS| " dpdklab
2024-07-31 12:14 ` |PENDING| " dpdklab
2024-07-31 12:14 ` dpdklab
2024-07-31 12:19 ` dpdklab
2024-07-31 12:21 ` dpdklab
2024-07-31 12:22 ` dpdklab
2024-07-31 12:23 ` dpdklab
2024-07-31 12:32 ` |SUCCESS| " dpdklab
2024-07-31 12:48 ` |PENDING| " dpdklab
2024-07-31 12:56 ` |SUCCESS| " dpdklab
2024-07-31 13:31 ` dpdklab
2024-07-31 13:40 ` dpdklab
2024-07-31 13:45 ` dpdklab
2024-07-31 13:50 ` dpdklab
2024-07-31 13:55 ` dpdklab
2024-07-31 14:14 ` dpdklab
2024-07-31 15:03 ` |PENDING| " dpdklab
2024-07-31 15:03 ` dpdklab
2024-07-31 15:04 ` dpdklab
2024-07-31 15:10 ` dpdklab
2024-07-31 15:11 ` dpdklab
2024-07-31 15:12 ` dpdklab
2024-07-31 15:13 ` dpdklab
2024-07-31 15:16 ` dpdklab
2024-07-31 15:17 ` dpdklab
2024-07-31 15:18 ` dpdklab
2024-07-31 15:18 ` dpdklab
2024-07-31 15:18 ` dpdklab [this message]
2024-07-31 15:19 ` dpdklab
2024-07-31 15:22 ` dpdklab
2024-07-31 15:23 ` |SUCCESS| " dpdklab
2024-07-31 15:29 ` |PENDING| " dpdklab
2024-07-31 15:30 ` dpdklab
2024-07-31 15:32 ` dpdklab
2024-07-31 15:33 ` dpdklab
2024-07-31 15:33 ` dpdklab
2024-07-31 15:40 ` dpdklab
2024-07-31 15:41 ` dpdklab
2024-07-31 15:41 ` dpdklab
2024-07-31 15:46 ` dpdklab
2024-07-31 16:07 ` |SUCCESS| " dpdklab
2024-07-31 16:58 ` |PENDING| " dpdklab
2024-07-31 17:01 ` dpdklab
2024-07-31 17:06 ` dpdklab
2024-07-31 17:07 ` dpdklab
2024-07-31 17:09 ` dpdklab
2024-07-31 17:11 ` dpdklab
2024-07-31 17:11 ` dpdklab
2024-07-31 17:12 ` dpdklab
2024-07-31 17:13 ` dpdklab
2024-07-31 17:14 ` dpdklab
2024-07-31 17:17 ` dpdklab
2024-07-31 17:18 ` dpdklab
2024-07-31 17:21 ` dpdklab
2024-07-31 17:22 ` dpdklab
2024-07-31 17:25 ` dpdklab
2024-07-31 17:26 ` dpdklab
2024-07-31 17:27 ` dpdklab
2024-07-31 17:30 ` dpdklab
2024-07-31 17:31 ` dpdklab
2024-07-31 17:41 ` dpdklab
2024-07-31 17:41 ` dpdklab
2024-07-31 17:46 ` |SUCCESS| " dpdklab
2024-07-31 17:47 ` |PENDING| " dpdklab
2024-07-31 17:49 ` dpdklab
2024-07-31 17:54 ` dpdklab
2024-07-31 17:56 ` dpdklab
2024-07-31 18:00 ` dpdklab
2024-07-31 18:03 ` dpdklab
2024-07-31 18:05 ` dpdklab
2024-07-31 18:10 ` |SUCCESS| " dpdklab
2024-07-31 18:13 ` |PENDING| " dpdklab
2024-07-31 18:30 ` dpdklab
2024-07-31 18:36 ` dpdklab
2024-07-31 18:47 ` dpdklab
2024-07-31 18:54 ` dpdklab
2024-07-31 19:02 ` dpdklab
2024-07-31 19:07 ` dpdklab
2024-07-31 19:09 ` dpdklab
2024-07-31 19:14 ` dpdklab
2024-07-31 19:15 ` dpdklab
2024-07-31 19:17 ` dpdklab
2024-07-31 19:17 ` dpdklab
2024-07-31 19:21 ` dpdklab
2024-07-31 19:24 ` dpdklab
2024-07-31 19:26 ` dpdklab
2024-07-31 19:26 ` dpdklab
2024-07-31 19:29 ` dpdklab
2024-07-31 19:30 ` dpdklab
2024-07-31 19:31 ` dpdklab
2024-07-31 19:36 ` dpdklab
2024-07-31 19:39 ` |SUCCESS| " dpdklab
2024-07-31 20:03 ` dpdklab
2024-08-01  5:03 ` 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=66aa55d3.050a0220.2f0a92.c56bSMTPIN_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).