From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139012-139013 [PATCH v1 2/2] deque: add unit tests for the deque library
Date: Mon, 1 Apr 2024 09:14:22 +0800 [thread overview]
Message-ID: <202404010114.4311EMsh641445@localhost.localdomain> (raw)
In-Reply-To: <20240401013729.1466298-3-aditya.ambadipudi@arm.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139013
_Compilation OK_
Submitter: Aditya Ambadipudi <aditya.ambadipudi@arm.com>
Date: Sun, 31 Mar 2024 20:37:28 -0500
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: a9778aad62470a38ccbb4e09a2a6bf0cc2e0e36d
139012-139013 --> 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-04-01 1:39 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240401013729.1466298-3-aditya.ambadipudi@arm.com>
2024-04-01 1:14 ` qemudev [this message]
2024-04-01 1:18 ` qemudev
2024-04-01 1:38 ` |WARNING| pw139013 " checkpatch
2024-04-01 2:17 ` |SUCCESS| pw139012-139013 [PATCH] [v1,2/2] deque: add unit tests for dpdklab
2024-04-01 2:17 ` dpdklab
2024-04-01 2:17 ` dpdklab
2024-04-01 2:17 ` dpdklab
2024-04-01 2:18 ` dpdklab
2024-04-01 2:18 ` dpdklab
2024-04-01 2:18 ` dpdklab
2024-04-01 2:19 ` dpdklab
2024-04-01 2:19 ` dpdklab
2024-04-01 2:19 ` dpdklab
2024-04-01 2:19 ` dpdklab
2024-04-01 2:20 ` dpdklab
2024-04-01 2:20 ` dpdklab
2024-04-01 2:20 ` dpdklab
2024-04-01 2:20 ` dpdklab
2024-04-01 2:20 ` dpdklab
2024-04-01 2:21 ` dpdklab
2024-04-01 2:21 ` dpdklab
2024-04-01 2:21 ` dpdklab
2024-04-01 2:21 ` dpdklab
2024-04-01 2:21 ` dpdklab
2024-04-01 2:22 ` dpdklab
2024-04-01 2:22 ` dpdklab
2024-04-01 2:22 ` dpdklab
2024-04-01 2:23 ` dpdklab
2024-04-01 2:23 ` dpdklab
2024-04-01 2:24 ` dpdklab
2024-04-01 2:24 ` dpdklab
2024-04-01 2:25 ` dpdklab
2024-04-01 2:25 ` dpdklab
2024-04-01 2:25 ` dpdklab
2024-04-01 2:26 ` dpdklab
2024-04-01 2:26 ` dpdklab
2024-04-01 2:26 ` dpdklab
2024-04-01 2:26 ` dpdklab
2024-04-01 2:27 ` dpdklab
2024-04-01 2:27 ` dpdklab
2024-04-01 2:28 ` dpdklab
2024-04-01 2:28 ` dpdklab
2024-04-01 2:29 ` dpdklab
2024-04-01 2:29 ` dpdklab
2024-04-01 2:31 ` dpdklab
2024-04-01 2:31 ` dpdklab
2024-04-01 2:31 ` dpdklab
2024-04-01 2:32 ` dpdklab
2024-04-01 2:32 ` dpdklab
2024-04-01 2:33 ` dpdklab
2024-04-01 2:33 ` dpdklab
2024-04-01 2:33 ` dpdklab
2024-04-01 2:33 ` dpdklab
2024-04-01 2:34 ` dpdklab
2024-04-01 2:34 ` dpdklab
2024-04-01 2:34 ` dpdklab
2024-04-01 2:36 ` dpdklab
2024-04-01 2:36 ` dpdklab
2024-04-01 2:36 ` dpdklab
2024-04-01 2:37 ` dpdklab
2024-04-01 2:38 ` dpdklab
2024-04-01 2:38 ` dpdklab
2024-04-01 2:38 ` dpdklab
2024-04-01 2:40 ` dpdklab
2024-04-01 2:40 ` dpdklab
2024-04-01 2:41 ` dpdklab
2024-04-01 2:42 ` dpdklab
2024-04-01 2:44 ` dpdklab
2024-04-01 2:45 ` dpdklab
2024-04-01 2:45 ` dpdklab
2024-04-01 2:47 ` dpdklab
2024-04-01 2:48 ` dpdklab
2024-04-01 2:48 ` dpdklab
2024-04-01 2:53 ` dpdklab
2024-04-01 2:56 ` dpdklab
2024-04-01 2:57 ` dpdklab
2024-04-01 2:57 ` dpdklab
2024-04-01 2:57 ` dpdklab
2024-04-01 2:58 ` dpdklab
2024-04-01 3:02 ` dpdklab
2024-04-01 3:05 ` dpdklab
2024-04-01 3:14 ` dpdklab
2024-04-01 3:32 ` dpdklab
2024-04-01 3:34 ` dpdklab
2024-04-01 4:25 ` |FAILURE| pw139013 [PATCH v1 2/2] deque: add unit tests for the deque library 0-day Robot
2024-04-03 10:10 ` |SUCCESS| pw139012-139013 [PATCH] [v1,2/2] deque: add unit tests for dpdklab
2024-04-03 10:13 ` dpdklab
2024-04-03 10:30 ` dpdklab
2024-04-03 10:31 ` dpdklab
2024-04-03 10:35 ` 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=202404010114.4311EMsh641445@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).