From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw142781 [PATCH] [v1,1/1] ml/cnxk: updates to cn10k error
Date: Wed, 31 Jul 2024 09:12:29 -0700 (PDT) [thread overview]
Message-ID: <66aa626d.810a0220.23447f.7d81SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240731063803.9223-1-syalavarthi@marvell.com>
Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/142781
_Testing pending_
Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Wednesday, July 31 2024 06:38:02
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:781d698ae2acb9bc7eed06f447cb8355673f7d81
142781 --> testing pending
Upstream job id: Generic-VM-DPDK-Compile-Meson#28398
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | 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
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/30670/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-07-31 16:12 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240731063803.9223-1-syalavarthi@marvell.com>
2024-07-31 6:27 ` |SUCCESS| pw142781 [PATCH v1 1/1] ml/cnxk: updates to cn10k error handling qemudev
2024-07-31 6:32 ` qemudev
2024-07-31 6:54 ` checkpatch
2024-07-31 7:42 ` 0-day Robot
2024-07-31 11:49 ` |SUCCESS| pw142781 [PATCH] [v1,1/1] ml/cnxk: updates to cn10k error dpdklab
2024-07-31 12:44 ` |PENDING| " dpdklab
2024-07-31 12:57 ` |SUCCESS| " dpdklab
2024-07-31 13:04 ` |PENDING| " dpdklab
2024-07-31 13:11 ` |SUCCESS| " dpdklab
2024-07-31 13:17 ` dpdklab
2024-07-31 13:20 ` dpdklab
2024-07-31 13:33 ` dpdklab
2024-07-31 13:40 ` |PENDING| " dpdklab
2024-07-31 13:42 ` dpdklab
2024-07-31 13:58 ` dpdklab
2024-07-31 14:00 ` |SUCCESS| " dpdklab
2024-07-31 14:00 ` |PENDING| " dpdklab
2024-07-31 14:02 ` dpdklab
2024-07-31 14:05 ` dpdklab
2024-07-31 14:05 ` dpdklab
2024-07-31 14:10 ` dpdklab
2024-07-31 14:10 ` dpdklab
2024-07-31 14:11 ` dpdklab
2024-07-31 14:11 ` dpdklab
2024-07-31 14:13 ` dpdklab
2024-07-31 14:31 ` dpdklab
2024-07-31 14:37 ` dpdklab
2024-07-31 15:31 ` dpdklab
2024-07-31 15:36 ` |SUCCESS| " dpdklab
2024-07-31 15:39 ` dpdklab
2024-07-31 16:12 ` dpdklab [this message]
2024-07-31 16:14 ` dpdklab
2024-07-31 16:17 ` |PENDING| " dpdklab
2024-07-31 16:18 ` dpdklab
2024-07-31 16:20 ` dpdklab
2024-07-31 16:39 ` dpdklab
2024-07-31 16:41 ` |SUCCESS| " dpdklab
2024-07-31 16:47 ` |PENDING| " dpdklab
2024-07-31 17:04 ` dpdklab
2024-07-31 17:11 ` dpdklab
2024-07-31 17:13 ` dpdklab
2024-07-31 17:15 ` dpdklab
2024-07-31 17:16 ` dpdklab
2024-07-31 17:17 ` dpdklab
2024-07-31 17:21 ` dpdklab
2024-07-31 17:23 ` dpdklab
2024-07-31 17:30 ` dpdklab
2024-07-31 17:38 ` dpdklab
2024-07-31 17:42 ` dpdklab
2024-07-31 17:43 ` dpdklab
2024-07-31 17:46 ` dpdklab
2024-07-31 17:47 ` dpdklab
2024-07-31 17:51 ` dpdklab
2024-07-31 17:52 ` dpdklab
2024-07-31 17:54 ` dpdklab
2024-07-31 17:55 ` dpdklab
2024-07-31 17:59 ` dpdklab
2024-07-31 18:03 ` dpdklab
2024-07-31 18:09 ` dpdklab
2024-07-31 18:09 ` dpdklab
2024-07-31 18:10 ` dpdklab
2024-07-31 18:12 ` |SUCCESS| " dpdklab
2024-07-31 18:16 ` |PENDING| " dpdklab
2024-07-31 18:17 ` |SUCCESS| " dpdklab
2024-07-31 18:20 ` |PENDING| " dpdklab
2024-07-31 18:21 ` |SUCCESS| " dpdklab
2024-07-31 18:25 ` dpdklab
2024-07-31 18:28 ` |PENDING| " dpdklab
2024-07-31 18:37 ` dpdklab
2024-07-31 18:44 ` dpdklab
2024-07-31 18:44 ` dpdklab
2024-07-31 18:45 ` |SUCCESS| " dpdklab
2024-07-31 18:47 ` |PENDING| " dpdklab
2024-07-31 18:54 ` dpdklab
2024-07-31 19:31 ` dpdklab
2024-07-31 19:34 ` dpdklab
2024-07-31 19:34 ` dpdklab
2024-07-31 19:35 ` dpdklab
2024-07-31 19:37 ` dpdklab
2024-07-31 19:38 ` dpdklab
2024-07-31 19:41 ` dpdklab
2024-07-31 19:41 ` dpdklab
2024-07-31 19:42 ` dpdklab
2024-07-31 19:47 ` dpdklab
2024-07-31 19:48 ` dpdklab
2024-07-31 19:50 ` dpdklab
2024-07-31 19:54 ` dpdklab
2024-07-31 19:54 ` dpdklab
2024-07-31 19:54 ` dpdklab
2024-07-31 19:57 ` dpdklab
2024-07-31 19:59 ` dpdklab
2024-07-31 20:01 ` dpdklab
2024-07-31 20:06 ` dpdklab
2024-07-31 20:09 ` |SUCCESS| " dpdklab
2024-07-31 20:15 ` dpdklab
2024-07-31 20:56 ` |PENDING| " dpdklab
2024-07-31 20:57 ` |SUCCESS| " dpdklab
2024-07-31 20:59 ` |PENDING| " dpdklab
2024-07-31 20:59 ` |SUCCESS| " dpdklab
2024-07-31 21:00 ` |PENDING| " dpdklab
2024-07-31 21:00 ` dpdklab
2024-07-31 21:01 ` dpdklab
2024-07-31 21:02 ` dpdklab
2024-07-31 21:07 ` dpdklab
2024-07-31 21:08 ` dpdklab
2024-07-31 21:11 ` dpdklab
2024-07-31 21:11 ` dpdklab
2024-07-31 21:13 ` dpdklab
2024-07-31 21:14 ` dpdklab
2024-07-31 21:16 ` dpdklab
2024-07-31 21:24 ` dpdklab
2024-07-31 21:27 ` dpdklab
2024-07-31 21:31 ` dpdklab
2024-07-31 21:39 ` dpdklab
2024-07-31 22:41 ` dpdklab
2024-07-31 22:54 ` |SUCCESS| " 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=66aa626d.810a0220.23447f.7d81SMTPIN_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).