From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139676-139677 [RFC v2 6/6] eal: add unit tests for atomic bit access functions
Date: Thu, 25 Apr 2024 16:45:15 +0800 [thread overview]
Message-ID: <202404250845.43P8jFRh1606802@localhost.localdomain> (raw)
In-Reply-To: <20240425085853.97888-7-mattias.ronnblom@ericsson.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139677
_Compilation OK_
Submitter: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
Date: Thu, 25 Apr 2024 10:58:48 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139676-139677 --> 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-25 9:13 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240425085853.97888-7-mattias.ronnblom@ericsson.com>
2024-04-25 8:45 ` qemudev [this message]
2024-04-25 8:49 ` qemudev
2024-04-25 9:44 ` |SUCCESS| pw139676-139677 [PATCH] [RFC,v2,6/6] eal: add unit tests f dpdklab
2024-04-25 9:44 ` |WARNING| " dpdklab
2024-04-25 9:45 ` dpdklab
2024-04-25 9:45 ` |SUCCESS| " dpdklab
2024-04-25 9:45 ` dpdklab
2024-04-25 9:45 ` dpdklab
2024-04-25 9:45 ` |WARNING| " dpdklab
2024-04-25 9:45 ` dpdklab
2024-04-25 9:46 ` |SUCCESS| " dpdklab
2024-04-25 9:46 ` |WARNING| " dpdklab
2024-04-25 9:46 ` dpdklab
2024-04-25 9:47 ` |SUCCESS| " dpdklab
2024-04-25 9:50 ` |FAILURE| " dpdklab
2024-04-25 9:51 ` |SUCCESS| " dpdklab
2024-04-25 9:52 ` dpdklab
2024-04-25 9:52 ` |FAILURE| " dpdklab
2024-04-25 9:53 ` |SUCCESS| " dpdklab
2024-04-25 9:55 ` dpdklab
2024-04-25 9:56 ` dpdklab
2024-04-25 9:56 ` dpdklab
2024-04-25 9:57 ` |FAILURE| " dpdklab
2024-04-25 9:57 ` |SUCCESS| " dpdklab
2024-04-25 9:58 ` dpdklab
2024-04-25 9:59 ` |FAILURE| " dpdklab
2024-04-25 9:59 ` |SUCCESS| " dpdklab
2024-04-25 10:05 ` dpdklab
2024-04-25 10:08 ` dpdklab
2024-04-25 10:08 ` dpdklab
2024-04-25 10:08 ` dpdklab
2024-04-25 10:08 ` dpdklab
2024-04-25 10:09 ` dpdklab
2024-04-25 10:09 ` dpdklab
2024-04-25 10:13 ` dpdklab
2024-04-25 10:20 ` dpdklab
2024-04-25 10:21 ` dpdklab
2024-04-25 10:21 ` |FAILURE| " dpdklab
2024-04-25 10:22 ` dpdklab
2024-04-25 10:23 ` dpdklab
2024-04-25 10:23 ` dpdklab
2024-04-25 10:24 ` dpdklab
2024-04-25 10:24 ` dpdklab
2024-04-25 10:25 ` dpdklab
2024-04-25 10:25 ` dpdklab
2024-04-25 10:25 ` |SUCCESS| " dpdklab
2024-04-25 10:26 ` dpdklab
2024-04-25 10:26 ` dpdklab
2024-04-25 10:27 ` |FAILURE| " dpdklab
2024-04-25 10:31 ` |SUCCESS| " dpdklab
2024-04-25 10:35 ` |FAILURE| " dpdklab
2024-04-25 10:35 ` dpdklab
2024-04-25 10:36 ` |SUCCESS| " dpdklab
2024-04-25 10:37 ` |FAILURE| " dpdklab
2024-04-25 10:37 ` dpdklab
2024-04-25 10:37 ` |SUCCESS| " dpdklab
2024-04-25 10:38 ` dpdklab
2024-04-25 10:38 ` |FAILURE| " dpdklab
2024-04-25 10:40 ` dpdklab
2024-04-25 10:44 ` dpdklab
2024-04-25 11:02 ` |SUCCESS| " dpdklab
2024-04-25 11:03 ` dpdklab
2024-04-25 11:03 ` dpdklab
2024-04-25 11:03 ` dpdklab
2024-04-25 11:04 ` dpdklab
2024-04-25 11:04 ` |FAILURE| " dpdklab
2024-04-25 11:05 ` dpdklab
2024-04-25 11:05 ` dpdklab
2024-04-25 11:06 ` dpdklab
2024-04-25 11:06 ` dpdklab
2024-04-25 11:15 ` |SUCCESS| " dpdklab
2024-04-25 11:16 ` dpdklab
2024-04-25 11:19 ` |FAILURE| " dpdklab
2024-04-25 11:20 ` dpdklab
2024-04-25 11:21 ` |SUCCESS| " dpdklab
2024-04-25 11:22 ` dpdklab
2024-04-25 11:29 ` dpdklab
2024-04-25 11:30 ` dpdklab
2024-04-25 11:33 ` dpdklab
2024-04-25 11:35 ` dpdklab
2024-04-25 11:36 ` dpdklab
2024-04-25 11:42 ` dpdklab
2024-04-25 11:44 ` dpdklab
2024-04-25 11:53 ` dpdklab
2024-04-25 11:59 ` dpdklab
2024-04-25 12:35 ` dpdklab
2024-04-25 13:02 ` dpdklab
2024-04-25 13:05 ` dpdklab
2024-04-25 13:53 ` 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=202404250845.43P8jFRh1606802@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).