From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143175-143176 [PATCH v1 2/2] usertools/cpu_layout: print out NUMA nodes
Date: Wed, 14 Aug 2024 18:52:31 +0800 [thread overview]
Message-ID: <202408141052.47EAqVvf2007148@localhost.localdomain> (raw)
In-Reply-To: <de03ee482c3623fd6d730c46a35d2a36ce43be49.1723634354.git.anatoly.burakov@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/143176
_Compilation OK_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Wed, 14 Aug 2024 12:19:18 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143175-143176 --> 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-08-14 11:21 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <de03ee482c3623fd6d730c46a35d2a36ce43be49.1723634354.git.anatoly.burakov@intel.com>
2024-08-14 10:52 ` qemudev [this message]
2024-08-14 10:57 ` qemudev
2024-08-14 11:21 ` |SUCCESS| pw143176 " checkpatch
2024-08-14 12:22 ` 0-day Robot
2024-08-14 16:30 ` |PENDING| pw143175-143176 [PATCH] [v1,2/2] usertools/cpu_layout: pri dpdklab
2024-08-14 16:32 ` |SUCCESS| " dpdklab
2024-08-14 16:34 ` |PENDING| " dpdklab
2024-08-14 16:35 ` dpdklab
2024-08-14 16:37 ` dpdklab
2024-08-14 16:38 ` dpdklab
2024-08-14 16:39 ` |SUCCESS| " dpdklab
2024-08-14 16:40 ` dpdklab
2024-08-14 16:40 ` |PENDING| " dpdklab
2024-08-14 16:40 ` dpdklab
2024-08-14 16:49 ` dpdklab
2024-08-14 16:52 ` |SUCCESS| " dpdklab
2024-08-14 16:53 ` dpdklab
2024-08-14 16:53 ` dpdklab
2024-08-14 16:53 ` dpdklab
2024-08-14 16:55 ` dpdklab
2024-08-14 16:55 ` dpdklab
2024-08-14 16:55 ` |PENDING| " dpdklab
2024-08-14 16:57 ` dpdklab
2024-08-14 16:57 ` dpdklab
2024-08-14 16:57 ` |SUCCESS| " dpdklab
2024-08-14 16:57 ` |PENDING| " dpdklab
2024-08-14 16:57 ` dpdklab
2024-08-14 16:58 ` dpdklab
2024-08-14 16:58 ` dpdklab
2024-08-14 16:58 ` dpdklab
2024-08-14 16:58 ` dpdklab
2024-08-14 16:59 ` dpdklab
2024-08-14 17:00 ` |SUCCESS| " dpdklab
2024-08-14 17:00 ` |PENDING| " dpdklab
2024-08-14 17:02 ` dpdklab
2024-08-14 17:04 ` dpdklab
2024-08-14 17:04 ` dpdklab
2024-08-14 17:04 ` dpdklab
2024-08-14 17:05 ` dpdklab
2024-08-14 17:05 ` dpdklab
2024-08-14 17:05 ` dpdklab
2024-08-14 17:05 ` dpdklab
2024-08-14 17:05 ` dpdklab
2024-08-14 17:06 ` dpdklab
2024-08-14 17:06 ` dpdklab
2024-08-14 17:06 ` dpdklab
2024-08-14 17:06 ` dpdklab
2024-08-14 17:06 ` dpdklab
2024-08-14 17:07 ` dpdklab
2024-08-14 17:07 ` dpdklab
2024-08-14 17:07 ` dpdklab
2024-08-14 17:09 ` dpdklab
2024-08-14 17:09 ` |SUCCESS| " dpdklab
2024-08-14 17:09 ` |PENDING| " dpdklab
2024-08-14 17:10 ` |SUCCESS| " dpdklab
2024-08-14 17:10 ` dpdklab
2024-08-14 17:11 ` |PENDING| " dpdklab
2024-08-14 17:12 ` dpdklab
2024-08-14 17:13 ` dpdklab
2024-08-14 17:14 ` dpdklab
2024-08-14 17:15 ` dpdklab
2024-08-14 17:15 ` dpdklab
2024-08-14 17:16 ` dpdklab
2024-08-14 17:19 ` dpdklab
2024-08-14 17:20 ` dpdklab
2024-08-14 17:22 ` dpdklab
2024-08-14 17:22 ` dpdklab
2024-08-14 17:22 ` dpdklab
2024-08-14 17:23 ` dpdklab
2024-08-14 17:25 ` dpdklab
2024-08-14 17:26 ` |SUCCESS| " dpdklab
2024-08-14 17:27 ` |PENDING| " dpdklab
2024-08-14 17:27 ` dpdklab
2024-08-14 17:29 ` dpdklab
2024-08-14 17:29 ` dpdklab
2024-08-14 17:31 ` dpdklab
2024-08-14 17:37 ` dpdklab
2024-08-14 17:42 ` dpdklab
2024-08-14 17:46 ` |SUCCESS| " dpdklab
2024-08-14 17:46 ` dpdklab
2024-08-14 17:47 ` |PENDING| " dpdklab
2024-08-14 17:48 ` dpdklab
2024-08-14 17:49 ` dpdklab
2024-08-14 17:52 ` dpdklab
2024-08-14 17:55 ` |SUCCESS| " dpdklab
2024-08-14 18:09 ` |PENDING| " dpdklab
2024-08-14 19:01 ` |SUCCESS| " dpdklab
2024-08-14 19:04 ` 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=202408141052.47EAqVvf2007148@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).