From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124542 [PATCH] service: split tests to perf and autotest to avoid spurious CI failures
Date: Sat, 25 Feb 2023 01:53:41 +0800 [thread overview]
Message-ID: <202302241753.31OHrfpR3755226@localhost.localdomain> (raw)
In-Reply-To: <20230224173637.243266-1-harry.van.haaren@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124542
_Compilation OK_
Submitter: Harry van Haaren <harry.van.haaren@intel.com>
Date: Fri, 24 Feb 2023 17:36:37 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7710b5d15a014872a3aaf646668dafa928ca8473
124542 --> 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:[~2023-02-24 18:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230224173637.243266-1-harry.van.haaren@intel.com>
2023-02-24 17:53 ` qemudev [this message]
2023-02-24 17:57 ` qemudev
2023-02-24 18:05 ` checkpatch
2023-02-24 20:39 ` 0-day Robot
2023-02-24 18:27 dpdklab
2023-02-24 18:31 dpdklab
2023-02-24 18:31 dpdklab
2023-02-24 18:32 dpdklab
2023-02-24 18:37 dpdklab
2023-02-24 18:40 dpdklab
2023-02-24 18:44 dpdklab
2023-02-24 18:45 dpdklab
2023-02-24 18:47 dpdklab
2023-02-24 18:52 dpdklab
2023-02-24 18:59 dpdklab
2023-02-24 19:08 dpdklab
2023-02-24 19:19 dpdklab
2023-02-24 19:25 dpdklab
2023-02-24 19:28 dpdklab
2023-02-24 19:29 dpdklab
2023-02-24 19:37 dpdklab
2023-02-24 19:37 dpdklab
2023-02-24 19:39 dpdklab
2023-02-24 19:40 dpdklab
2023-02-24 19:42 dpdklab
2023-02-24 19:44 dpdklab
2023-02-24 19:48 dpdklab
2023-02-24 19:48 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=202302241753.31OHrfpR3755226@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).