From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw155199 [PATCH] [v0,1/1] net/octeon_ep: fix device start
Date: Mon, 14 Jul 2025 03:55:34 -0700 (PDT) [thread overview]
Message-ID: <6874e226.050a0220.2f77b4.9189SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250714055849.2258453-1-vattunuru@marvell.com>
Test-Label: iol-compile-arm64-testing
Test-Status: PENDING
http://dpdk.org/patch/155199
_Testing pending_
Submitter: Vamsi Krishna Attunuru <vattunuru@marvell.com>
Date: Monday, July 14 2025 05:58:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:3761152ec7f99c9b60c9cc933102d35fa663393a
155199 --> testing pending
Upstream job id: Generic-DPDK-Compile-Meson#408508
Test environment and result as below:
+------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+==============================+====================+
| Red Hat Enterprise Linux 9.5 | PEND |
+------------------------------+--------------------+
| Ubuntu 20.04 | PEND |
+------------------------------+--------------------+
| Debian GNU/Linux 12 | PEND |
+------------------------------+--------------------+
| Fedora Linux 40 | PEND |
+------------------------------+--------------------+
| Fedora Linux 41 | PEND |
+------------------------------+--------------------+
| Ubuntu 22.04 | PEND |
+------------------------------+--------------------+
Red Hat Enterprise Linux 9.5
Kernel: 5.4
Compiler: gcc gcc (GCC) 11.5.0 20240719 (Red Hat 11.5.0-2)
Ubuntu 20.04
Kernel: 5.15
Compiler: aarch64-linux-gnu-gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Debian GNU/Linux 12
Kernel: 5.4
Compiler: gcc gcc (Debian 12.2.0-14+deb12u1) 12.2.0
Fedora Linux 40
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora Linux 41
Kernel: 5.4
Compiler: gcc gcc (GCC) 14.3.1 20250523 (Red Hat 14.3.1-1)
Ubuntu 22.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33646/
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:[~2025-07-14 10:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250714055849.2258453-1-vattunuru@marvell.com>
2025-07-14 5:31 ` |SUCCESS| pw155199 [PATCH v0 1/1] net/octeon_ep: fix device start routine qemudev
2025-07-14 5:35 ` qemudev
2025-07-14 5:58 ` checkpatch
2025-07-14 6:49 ` |PENDING| pw155199 [PATCH] [v0,1/1] net/octeon_ep: fix device start dpdklab
2025-07-14 7:01 ` |SUCCESS| " dpdklab
2025-07-14 7:02 ` dpdklab
2025-07-14 7:03 ` |SUCCESS| pw155199 [PATCH v0 1/1] net/octeon_ep: fix device start routine 0-day Robot
2025-07-14 7:34 ` |PENDING| pw155199 [PATCH] [v0,1/1] net/octeon_ep: fix device start dpdklab
2025-07-14 7:54 ` |SUCCESS| " dpdklab
2025-07-14 8:10 ` dpdklab
2025-07-14 8:18 ` |PENDING| " dpdklab
2025-07-14 8:20 ` |SUCCESS| " dpdklab
2025-07-14 8:37 ` dpdklab
2025-07-14 9:01 ` dpdklab
2025-07-14 10:16 ` dpdklab
2025-07-14 10:55 ` dpdklab [this message]
2025-07-14 11:15 ` dpdklab
2025-07-14 11:16 ` dpdklab
2025-07-14 11:17 ` dpdklab
2025-07-14 11:18 ` dpdklab
2025-07-14 13:33 ` dpdklab
2025-07-14 14:06 ` dpdklab
2025-07-14 16:15 ` dpdklab
2025-07-14 16:23 ` 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=6874e226.050a0220.2f77b4.9189SMTPIN_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).