From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139718-139722 [RFC v3 6/6] eal: add unit tests for atomic bit access functions
Date: Mon, 29 Apr 2024 17:42:39 +0800 [thread overview]
Message-ID: <202404290942.43T9gdU12964036@localhost.localdomain> (raw)
In-Reply-To: <20240429095138.106849-7-mattias.ronnblom@ericsson.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139722
_Compilation OK_
Submitter: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
Date: Mon, 29 Apr 2024 11:51:33 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139718-139722 --> 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-29 10:10 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240429095138.106849-7-mattias.ronnblom@ericsson.com>
2024-04-29 9:42 ` qemudev [this message]
2024-04-29 9:47 ` qemudev
2024-04-29 11:04 ` |FAILURE| pw139722 " 0-day Robot
2024-04-29 14:31 ` |SUCCESS| pw139718-139722 [PATCH] [RFC,v3,6/6] eal: add unit tests f dpdklab
2024-04-29 14:31 ` dpdklab
2024-04-29 14:32 ` dpdklab
2024-04-29 14:32 ` dpdklab
2024-04-29 14:33 ` dpdklab
2024-04-29 14:33 ` dpdklab
2024-04-29 14:34 ` dpdklab
2024-04-29 14:35 ` dpdklab
2024-04-29 14:35 ` dpdklab
2024-04-29 14:36 ` dpdklab
2024-04-29 14:36 ` dpdklab
2024-04-29 14:37 ` dpdklab
2024-04-29 14:37 ` dpdklab
2024-04-29 14:38 ` dpdklab
2024-04-29 14:38 ` dpdklab
2024-04-29 14:38 ` dpdklab
2024-04-29 14:39 ` dpdklab
2024-04-29 14:39 ` dpdklab
2024-04-29 14:39 ` dpdklab
2024-04-29 14:39 ` dpdklab
2024-04-29 14:40 ` dpdklab
2024-04-29 14:43 ` dpdklab
2024-04-29 14:47 ` dpdklab
2024-04-29 14:47 ` dpdklab
2024-04-29 14:48 ` dpdklab
2024-04-29 14:48 ` dpdklab
2024-04-29 14:49 ` dpdklab
2024-04-29 14:49 ` dpdklab
2024-04-29 14:51 ` dpdklab
2024-04-29 14:54 ` dpdklab
2024-04-29 14:57 ` dpdklab
2024-04-29 14:58 ` dpdklab
2024-04-29 14:58 ` dpdklab
2024-04-29 14:59 ` dpdklab
2024-04-29 14:59 ` dpdklab
2024-04-29 15:02 ` dpdklab
2024-04-29 15:03 ` dpdklab
2024-04-29 15:04 ` dpdklab
2024-04-29 15:04 ` dpdklab
2024-04-29 15:06 ` dpdklab
2024-04-29 15:07 ` dpdklab
2024-04-29 15:07 ` dpdklab
2024-04-29 15:08 ` dpdklab
2024-04-29 15:10 ` dpdklab
2024-04-29 15:10 ` dpdklab
2024-04-29 15:10 ` dpdklab
2024-04-29 15:11 ` dpdklab
2024-04-29 15:12 ` dpdklab
2024-04-29 15:14 ` dpdklab
2024-04-29 15:14 ` dpdklab
2024-04-29 15:14 ` dpdklab
2024-04-29 15:18 ` dpdklab
2024-04-29 15:18 ` |FAILURE| " dpdklab
2024-04-29 15:20 ` |SUCCESS| " dpdklab
2024-04-29 15:22 ` |FAILURE| " dpdklab
2024-04-29 15:24 ` |SUCCESS| " dpdklab
2024-04-29 15:24 ` |FAILURE| " dpdklab
2024-04-29 15:24 ` |SUCCESS| " dpdklab
2024-04-29 15:25 ` dpdklab
2024-04-29 15:27 ` dpdklab
2024-04-29 15:28 ` dpdklab
2024-04-29 15:29 ` dpdklab
2024-04-29 15:29 ` |FAILURE| " dpdklab
2024-04-29 15:29 ` dpdklab
2024-04-29 15:32 ` |SUCCESS| " dpdklab
2024-04-29 15:32 ` dpdklab
2024-04-29 15:33 ` |FAILURE| " dpdklab
2024-04-29 15:36 ` |SUCCESS| " dpdklab
2024-04-29 15:37 ` dpdklab
2024-04-29 15:37 ` |FAILURE| " dpdklab
2024-04-29 15:37 ` |SUCCESS| " dpdklab
2024-04-29 15:37 ` dpdklab
2024-04-29 15:37 ` dpdklab
2024-04-29 15:39 ` dpdklab
2024-04-29 15:41 ` dpdklab
2024-04-29 15:41 ` |FAILURE| " dpdklab
2024-04-29 15:42 ` dpdklab
2024-04-29 15:45 ` |SUCCESS| " dpdklab
2024-04-29 15:46 ` dpdklab
2024-04-29 15:46 ` dpdklab
2024-04-29 15:49 ` |FAILURE| " dpdklab
2024-04-29 16:01 ` |SUCCESS| " dpdklab
2024-04-29 16:01 ` dpdklab
2024-04-29 16:32 ` dpdklab
2024-04-29 17:12 ` 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=202404290942.43T9gdU12964036@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).