From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw154348 [PATCH] test/event: fix event vector adapter timeouts
Date: Thu, 12 Jun 2025 07:39:21 +0800 [thread overview]
Message-ID: <202506112339.55BNdLfU1094397@localhost.localdomain> (raw)
In-Reply-To: <20250612001338.71098-1-pbhagavatula@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/154348
_Compilation OK_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Thu, 12 Jun 2025 05:43:38 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: dbe1f0a9446edfa62c4af8620d73ed342f4cfba0
154348 --> meson & ninja build successfully
Test environment and result as below:
+---------------------+----------------+
| Environment | compilation |
+---------------------+----------------+
| Loongnix-Server 8.3 | PASS |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
next parent reply other threads:[~2025-06-12 0:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250612001338.71098-1-pbhagavatula@marvell.com>
2025-06-11 23:39 ` qemudev [this message]
2025-06-11 23:44 ` qemudev
2025-06-12 0:12 ` checkpatch
2025-06-12 0:52 ` |PENDING| pw154348 [PATCH] test/event: fix event vector adapter time dpdklab
2025-06-12 0:58 ` |SUCCESS| " dpdklab
2025-06-12 1:00 ` dpdklab
2025-06-12 1:08 ` |PENDING| " dpdklab
2025-06-12 1:08 ` |SUCCESS| " dpdklab
2025-06-12 1:13 ` dpdklab
2025-06-12 1:15 ` |PENDING| " dpdklab
2025-06-12 1:15 ` |SUCCESS| " dpdklab
2025-06-12 1:24 ` |SUCCESS| pw154348 [PATCH] test/event: fix event vector adapter timeouts 0-day Robot
2025-06-12 1:34 ` |PENDING| pw154348 [PATCH] test/event: fix event vector adapter time dpdklab
2025-06-12 1:36 ` dpdklab
2025-06-12 1:52 ` |SUCCESS| " dpdklab
2025-06-12 2:26 ` dpdklab
2025-06-12 3:41 ` dpdklab
2025-06-12 3:52 ` |WARNING| " dpdklab
2025-06-12 4:34 ` dpdklab
2025-06-12 4:35 ` dpdklab
2025-06-12 4:48 ` |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=202506112339.55BNdLfU1094397@localhost.localdomain \
--to=qemudev@loongson.cn \
--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).