From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139091-139092 [PATCH v2 2/2] test: add functional test for uuid
Date: Thu, 4 Apr 2024 05:50:36 +0800 [thread overview]
Message-ID: <202404032150.433Loaut2021950@localhost.localdomain> (raw)
In-Reply-To: <20240403221319.499014-3-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139092
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wed, 3 Apr 2024 15:11:07 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139091-139092 --> 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-03 22:15 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240403221319.499014-3-stephen@networkplumber.org>
2024-04-03 21:50 ` qemudev [this message]
2024-04-03 21:55 ` qemudev
2024-04-03 22:13 ` |WARNING| pw139092 " checkpatch
2024-04-03 23:05 ` |FAILURE| " 0-day Robot
2024-04-03 23:13 ` |SUCCESS| pw139091-139092 [PATCH] [v2,2/2] test: add functional test dpdklab
2024-04-03 23:16 ` |FAILURE| " dpdklab
2024-04-03 23:17 ` |SUCCESS| " dpdklab
2024-04-03 23:17 ` |FAILURE| " dpdklab
2024-04-03 23:18 ` dpdklab
2024-04-03 23:18 ` |SUCCESS| " dpdklab
2024-04-03 23:18 ` dpdklab
2024-04-03 23:19 ` dpdklab
2024-04-03 23:19 ` dpdklab
2024-04-03 23:19 ` |FAILURE| " dpdklab
2024-04-03 23:19 ` dpdklab
2024-04-03 23:20 ` dpdklab
2024-04-03 23:20 ` |SUCCESS| " dpdklab
2024-04-03 23:23 ` dpdklab
2024-04-03 23:23 ` dpdklab
2024-04-03 23:23 ` dpdklab
2024-04-03 23:24 ` dpdklab
2024-04-03 23:24 ` dpdklab
2024-04-03 23:24 ` dpdklab
2024-04-03 23:24 ` dpdklab
2024-04-03 23:25 ` dpdklab
2024-04-03 23:25 ` dpdklab
2024-04-03 23:25 ` dpdklab
2024-04-03 23:25 ` dpdklab
2024-04-03 23:26 ` dpdklab
2024-04-03 23:26 ` dpdklab
2024-04-03 23:27 ` dpdklab
2024-04-03 23:27 ` dpdklab
2024-04-03 23:27 ` dpdklab
2024-04-03 23:28 ` dpdklab
2024-04-03 23:28 ` dpdklab
2024-04-03 23:29 ` dpdklab
2024-04-03 23:38 ` dpdklab
2024-04-03 23:38 ` dpdklab
2024-04-03 23:39 ` dpdklab
2024-04-03 23:39 ` |FAILURE| " dpdklab
2024-04-03 23:41 ` dpdklab
2024-04-03 23:44 ` |SUCCESS| " dpdklab
2024-04-03 23:44 ` dpdklab
2024-04-03 23:44 ` dpdklab
2024-04-03 23:45 ` |FAILURE| " dpdklab
2024-04-03 23:45 ` |SUCCESS| " dpdklab
2024-04-03 23:46 ` |FAILURE| " dpdklab
2024-04-03 23:46 ` |SUCCESS| " dpdklab
2024-04-03 23:46 ` dpdklab
2024-04-03 23:47 ` |FAILURE| " dpdklab
2024-04-03 23:47 ` dpdklab
2024-04-03 23:57 ` dpdklab
2024-04-03 23:57 ` dpdklab
2024-04-03 23:59 ` |SUCCESS| " dpdklab
2024-04-03 23:59 ` dpdklab
2024-04-04 0:00 ` |FAILURE| " dpdklab
2024-04-04 0:00 ` |SUCCESS| " dpdklab
2024-04-04 0:01 ` dpdklab
2024-04-04 0:01 ` |FAILURE| " dpdklab
2024-04-04 0:02 ` |SUCCESS| " dpdklab
2024-04-04 0:02 ` dpdklab
2024-04-04 0:02 ` dpdklab
2024-04-04 0:03 ` dpdklab
2024-04-04 0:04 ` dpdklab
2024-04-04 0:05 ` |FAILURE| " dpdklab
2024-04-04 0:12 ` dpdklab
2024-04-04 0:13 ` |SUCCESS| " dpdklab
2024-04-04 0:43 ` dpdklab
2024-04-04 0:44 ` dpdklab
2024-04-04 0:54 ` dpdklab
2024-04-04 0:58 ` dpdklab
2024-04-04 0:59 ` dpdklab
2024-04-04 1:02 ` dpdklab
2024-04-04 1:12 ` dpdklab
2024-04-04 1:14 ` dpdklab
2024-04-04 1:15 ` dpdklab
2024-04-04 1:16 ` dpdklab
2024-04-04 1:17 ` dpdklab
2024-04-04 1:17 ` dpdklab
2024-04-04 1:18 ` dpdklab
2024-04-04 1:20 ` dpdklab
2024-04-04 1:54 ` |FAILURE| " dpdklab
2024-04-04 1:57 ` dpdklab
2024-04-04 2:04 ` |SUCCESS| " dpdklab
2024-04-04 2:29 ` dpdklab
2024-04-04 11:57 ` dpdklab
2024-04-04 12:03 ` dpdklab
2024-04-04 12:07 ` dpdklab
2024-04-04 12:11 ` dpdklab
2024-04-04 12:15 ` 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=202404032150.433Loaut2021950@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).