From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139867-139872 [RFC v7 6/6] eal: add unit tests for atomic bit access functions
Date: Sun, 5 May 2024 16:23:47 +0800 [thread overview]
Message-ID: <202405050823.4458NlKb1332015@localhost.localdomain> (raw)
In-Reply-To: <20240505083737.118649-7-mattias.ronnblom@ericsson.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139872
_Compilation OK_
Submitter: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
Date: Sun, 5 May 2024 10:37:32 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139867-139872 --> 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-05-05 8:51 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240505083737.118649-7-mattias.ronnblom@ericsson.com>
2024-05-05 8:23 ` qemudev [this message]
2024-05-05 8:28 ` qemudev
2024-05-05 9:26 ` |SUCCESS| pw139867-139872 [PATCH] [RFC,v7,6/6] eal: add unit tests f dpdklab
2024-05-05 9:27 ` dpdklab
2024-05-05 9:27 ` dpdklab
2024-05-05 9:27 ` dpdklab
2024-05-05 9:28 ` dpdklab
2024-05-05 9:28 ` dpdklab
2024-05-05 9:28 ` dpdklab
2024-05-05 9:28 ` dpdklab
2024-05-05 9:28 ` dpdklab
2024-05-05 9:31 ` dpdklab
2024-05-05 9:32 ` dpdklab
2024-05-05 9:34 ` dpdklab
2024-05-05 9:34 ` dpdklab
2024-05-05 9:35 ` dpdklab
2024-05-05 9:36 ` dpdklab
2024-05-05 9:38 ` dpdklab
2024-05-05 9:39 ` dpdklab
2024-05-05 9:41 ` dpdklab
2024-05-05 9:43 ` dpdklab
2024-05-05 9:43 ` dpdklab
2024-05-05 9:43 ` |FAILURE| pw139872 [RFC v7 6/6] eal: add unit tests for atomic bit access functions 0-day Robot
2024-05-05 9:44 ` |SUCCESS| pw139867-139872 [PATCH] [RFC,v7,6/6] eal: add unit tests f dpdklab
2024-05-05 9:44 ` dpdklab
2024-05-05 9:46 ` dpdklab
2024-05-05 9:48 ` dpdklab
2024-05-05 9:48 ` dpdklab
2024-05-05 9:49 ` dpdklab
2024-05-05 9:49 ` dpdklab
2024-05-05 9:50 ` dpdklab
2024-05-05 9:52 ` dpdklab
2024-05-05 9:52 ` dpdklab
2024-05-05 9:54 ` dpdklab
2024-05-05 9:54 ` dpdklab
2024-05-05 9:56 ` dpdklab
2024-05-05 9:58 ` dpdklab
2024-05-05 10:00 ` dpdklab
2024-05-05 10:01 ` dpdklab
2024-05-05 10:01 ` dpdklab
2024-05-05 10:01 ` dpdklab
2024-05-05 10:03 ` dpdklab
2024-05-05 10:03 ` dpdklab
2024-05-05 10:05 ` dpdklab
2024-05-05 10:06 ` dpdklab
2024-05-05 10:06 ` dpdklab
2024-05-05 10:06 ` dpdklab
2024-05-05 10:07 ` dpdklab
2024-05-05 10:08 ` |FAILURE| " dpdklab
2024-05-05 10:10 ` |SUCCESS| " dpdklab
2024-05-05 10:14 ` |FAILURE| " dpdklab
2024-05-05 10:16 ` |SUCCESS| " dpdklab
2024-05-05 10:17 ` |FAILURE| " dpdklab
2024-05-05 10:18 ` |SUCCESS| " dpdklab
2024-05-05 10:19 ` dpdklab
2024-05-05 10:20 ` |FAILURE| " dpdklab
2024-05-05 10:22 ` |SUCCESS| " dpdklab
2024-05-05 10:23 ` dpdklab
2024-05-05 10:24 ` dpdklab
2024-05-05 10:24 ` dpdklab
2024-05-05 10:25 ` dpdklab
2024-05-05 10:25 ` |FAILURE| " dpdklab
2024-05-05 10:25 ` dpdklab
2024-05-05 10:29 ` dpdklab
2024-05-05 10:32 ` dpdklab
2024-05-05 10:33 ` |SUCCESS| " dpdklab
2024-05-05 10:36 ` |FAILURE| " dpdklab
2024-05-05 10:38 ` dpdklab
2024-05-05 10:44 ` |SUCCESS| " dpdklab
2024-05-05 10:47 ` dpdklab
2024-05-05 10:57 ` dpdklab
2024-05-05 10:57 ` dpdklab
2024-05-05 11:00 ` dpdklab
2024-05-05 11:00 ` dpdklab
2024-05-05 11:04 ` dpdklab
2024-05-05 11:20 ` dpdklab
2024-05-05 11:25 ` dpdklab
2024-05-05 11:27 ` dpdklab
2024-05-05 12:27 ` dpdklab
2024-05-05 12:45 ` dpdklab
2024-05-05 12:51 ` dpdklab
2024-05-05 13:06 ` dpdklab
2024-05-05 16:40 ` dpdklab
2024-05-05 16:44 ` dpdklab
2024-05-05 16:48 ` dpdklab
2024-05-05 17:07 ` dpdklab
2024-05-05 17:11 ` dpdklab
2024-05-06 15:02 ` dpdklab
2024-05-06 18:52 ` |WARNING| pw139872 [RFC v7 6/6] eal: add unit tests for atomic bit access functions checkpatch
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=202405050823.4458NlKb1332015@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).