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