From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120503-120505 [PATCH v2 3/3] test/bbdev: explicit check for allocation failure
Date: Sat, 10 Dec 2022 08:44:19 +0800 [thread overview]
Message-ID: <202212100044.2BA0iJfw1021193@localhost.localdomain> (raw)
In-Reply-To: <20221206191441.12428-4-nicolas.chautru@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/120505
_Compilation OK_
Submitter: Nicolas Chautru <nicolas.chautru@intel.com>
Date: Tue, 6 Dec 2022 11:14:39 -0800
DPDK git baseline: Repo:dpdk-next-crypto
Branch: for-main
CommitID: 7b1934d01a1a8afa1391f361088d8285d100e62a
120503-120505 --> 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 prev parent reply other threads:[~2022-12-10 0:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221206191441.12428-4-nicolas.chautru@intel.com>
2022-12-06 19:16 ` |SUCCESS| pw120505 " checkpatch
2022-12-06 20:38 ` 0-day Robot
2022-12-08 16:19 ` |SUCCESS| pw120503-120505 " qemudev
2022-12-08 16:19 ` qemudev
2022-12-08 16:55 ` qemudev
2022-12-08 16:55 ` qemudev
2022-12-09 4:12 ` qemudev
2022-12-09 4:12 ` qemudev
2022-12-10 0:44 ` qemudev [this message]
2022-12-10 0:44 ` qemudev
2022-12-07 5:21 |SUCCESS| pw120503-120505 [PATCH] [v2, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2022-12-07 1:29 dpdklab
2022-12-06 23:56 dpdklab
2022-12-06 23:56 dpdklab
2022-12-06 23:53 dpdklab
2022-12-06 23:50 dpdklab
2022-12-06 23:50 dpdklab
2022-12-06 23:49 dpdklab
2022-12-06 23:49 dpdklab
2022-12-06 23:49 dpdklab
2022-12-06 23:35 dpdklab
2022-12-06 21:21 dpdklab
2022-12-06 20:01 dpdklab
2022-12-06 19:54 dpdklab
2022-12-06 19:44 dpdklab
2022-12-06 19:41 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=202212100044.2BA0iJfw1021193@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).