From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138100 [PATCH] test/lcores: reduce cpu consumption
Date: Thu, 7 Mar 2024 19:09:58 +0800 [thread overview]
Message-ID: <202403071109.427B9wBN277354@localhost.localdomain> (raw)
In-Reply-To: <20240307113324.845309-1-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138100
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Thu, 7 Mar 2024 12:33:24 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 19082c1fac430c74bb4b1c101edd12d88928e7c2
138100 --> 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:[~2024-03-07 11:34 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240307113324.845309-1-david.marchand@redhat.com>
2024-03-07 11:09 ` qemudev [this message]
2024-03-07 11:14 ` qemudev
2024-03-07 11:34 ` checkpatch
2024-03-07 12:24 ` |FAILURE| " 0-day Robot
2024-03-07 12:51 ` |SUCCESS| " dpdklab
2024-03-07 13:02 ` dpdklab
2024-03-07 13:03 ` dpdklab
2024-03-07 13:07 ` dpdklab
2024-03-07 13:12 ` dpdklab
2024-03-07 13:12 ` dpdklab
2024-03-07 13:21 ` dpdklab
2024-03-07 13:35 ` dpdklab
2024-03-07 13:36 ` dpdklab
2024-03-07 13:44 ` dpdklab
2024-03-07 13:44 ` dpdklab
2024-03-07 13:45 ` dpdklab
2024-03-07 13:45 ` dpdklab
2024-03-07 13:45 ` dpdklab
2024-03-07 13:47 ` dpdklab
2024-03-07 13:47 ` dpdklab
2024-03-07 13:48 ` dpdklab
2024-03-07 13:48 ` dpdklab
2024-03-07 14:07 ` |FAILURE| " dpdklab
2024-03-07 14:08 ` dpdklab
2024-03-07 14:09 ` |SUCCESS| " dpdklab
2024-03-07 14:11 ` |FAILURE| " dpdklab
2024-03-07 14:12 ` dpdklab
2024-03-07 14:12 ` |SUCCESS| " dpdklab
2024-03-07 14:12 ` dpdklab
2024-03-07 14:13 ` dpdklab
2024-03-07 14:13 ` dpdklab
2024-03-07 14:13 ` |FAILURE| " dpdklab
2024-03-07 14:14 ` |SUCCESS| " dpdklab
2024-03-07 14:14 ` |FAILURE| " dpdklab
2024-03-07 14:15 ` dpdklab
2024-03-07 14:18 ` dpdklab
2024-03-07 14:19 ` dpdklab
2024-03-07 14:20 ` |SUCCESS| " dpdklab
2024-03-07 14:20 ` |FAILURE| " dpdklab
2024-03-07 14:20 ` |SUCCESS| " dpdklab
2024-03-07 14:20 ` dpdklab
2024-03-07 14:21 ` dpdklab
2024-03-07 14:21 ` dpdklab
2024-03-07 14:21 ` dpdklab
2024-03-07 14:22 ` dpdklab
2024-03-07 14:22 ` dpdklab
2024-03-07 14:29 ` dpdklab
2024-03-07 14:29 ` dpdklab
2024-03-07 14:30 ` dpdklab
2024-03-07 14:31 ` dpdklab
2024-03-07 14:32 ` dpdklab
2024-03-07 14:32 ` dpdklab
2024-03-07 14:33 ` dpdklab
2024-03-07 14:33 ` |FAILURE| " dpdklab
2024-03-07 14:34 ` dpdklab
2024-03-07 14:34 ` |SUCCESS| " dpdklab
2024-03-07 14:34 ` dpdklab
2024-03-07 14:35 ` dpdklab
2024-03-07 14:35 ` |FAILURE| " dpdklab
2024-03-07 14:36 ` |SUCCESS| " dpdklab
2024-03-07 14:37 ` dpdklab
2024-03-07 14:38 ` dpdklab
2024-03-07 14:40 ` dpdklab
2024-03-07 14:48 ` dpdklab
2024-03-07 14:50 ` dpdklab
2024-03-07 14:51 ` dpdklab
2024-03-07 15:24 ` dpdklab
2024-03-07 16:44 ` |FAILURE| " dpdklab
2024-03-07 21:05 ` |SUCCESS| " dpdklab
2024-03-08 5:26 ` dpdklab
2024-03-08 5:27 ` dpdklab
2024-03-08 5:32 ` dpdklab
2024-03-08 5:32 ` dpdklab
2024-03-11 20:00 ` dpdklab
2024-03-11 20:36 ` 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=202403071109.427B9wBN277354@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).