From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124738-124753 [PATCH v3 17/17] test/bbdev: remove iter count from bler test
Date: Mon, 6 Mar 2023 15:15:23 +0800 [thread overview]
Message-ID: <202303060715.3267FNU83957556@localhost.localdomain> (raw)
In-Reply-To: <20230302202211.170017-18-hernan.vargas@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124753
_Compilation OK_
Submitter: Hernan Vargas <hernan.vargas@intel.com>
Date: Thu, 2 Mar 2023 12:21:55 -0800
DPDK git baseline: Repo:dpdk-next-baseband
Branch: for-main
CommitID: 3ba3030b4fab3f31fd7c22dc24c7b83f0404811a
124738-124753 --> 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:[~2023-03-06 7:29 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230302202211.170017-18-hernan.vargas@intel.com>
2023-03-02 20:25 ` |SUCCESS| pw124753 " checkpatch
2023-03-02 22:19 ` 0-day Robot
2023-03-06 7:15 ` qemudev [this message]
2023-03-06 7:15 ` |SUCCESS| pw124738-124753 " qemudev
2023-03-03 4:37 |SUCCESS| pw124738-124753 [PATCH] [v3, " dpdklab
2023-03-03 4:42 dpdklab
2023-03-03 4:46 dpdklab
2023-03-03 4:47 dpdklab
2023-03-03 4:47 dpdklab
2023-03-03 4:48 dpdklab
2023-03-03 4:50 dpdklab
2023-03-03 4:54 dpdklab
2023-03-03 4:54 dpdklab
2023-03-03 4:54 dpdklab
2023-03-03 5:03 dpdklab
2023-03-03 5:06 dpdklab
2023-03-03 5:12 dpdklab
2023-03-03 5:19 dpdklab
2023-03-03 5:21 dpdklab
2023-03-03 5:22 dpdklab
2023-03-03 5:22 dpdklab
2023-03-03 5:24 dpdklab
2023-03-03 5:24 dpdklab
2023-03-03 5:28 dpdklab
2023-03-03 5:28 dpdklab
2023-03-03 5:30 dpdklab
2023-03-03 5:30 dpdklab
2023-03-03 5:38 dpdklab
2023-03-03 5:43 dpdklab
2023-03-03 6:19 dpdklab
2023-03-03 7:23 dpdklab
2023-03-03 8:29 dpdklab
2023-03-03 9:24 dpdklab
2023-03-03 10:53 dpdklab
2023-03-03 17:55 dpdklab
2023-03-03 19:59 dpdklab
2023-03-04 18:26 dpdklab
2023-03-04 18:38 dpdklab
2023-03-04 18:40 dpdklab
2023-03-04 18:41 dpdklab
2023-03-04 18:43 dpdklab
2023-03-04 18:53 dpdklab
2023-03-04 18:55 dpdklab
2023-03-04 19:01 dpdklab
2023-03-04 19:04 dpdklab
2023-03-04 19:10 dpdklab
2023-03-04 19:14 dpdklab
2023-03-04 19:15 dpdklab
2023-03-04 19:16 dpdklab
2023-03-04 19:16 dpdklab
2023-03-04 19:17 dpdklab
2023-03-04 19:20 dpdklab
2023-03-04 19:24 dpdklab
2023-03-04 19:26 dpdklab
2023-03-04 19:28 dpdklab
2023-03-04 19:29 dpdklab
2023-03-04 19:30 dpdklab
2023-03-04 19:31 dpdklab
2023-03-04 19:39 dpdklab
2023-03-04 19:39 dpdklab
2023-03-04 19:52 dpdklab
2023-03-04 19:55 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=202303060715.3267FNU83957556@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).