From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139704-139703 [RFC PATCH 2/2] graph: add ip4 output feature arc
Date: Fri, 26 Apr 2024 19:58:00 +0800 [thread overview]
Message-ID: <202404261158.43QBw0sD2437135@localhost.localdomain> (raw)
In-Reply-To: <20240426122203.32357-3-nsaxena@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139703
_Compilation OK_
Submitter: Nitin Saxena <nsaxena@marvell.com>
Date: Fri, 26 Apr 2024 17:52:02 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139704-139703 --> 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-26 12:25 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240426122203.32357-3-nsaxena@marvell.com>
2024-04-26 11:58 ` qemudev [this message]
2024-04-26 12:02 ` qemudev
2024-04-26 16:26 ` |SUCCESS| pw139704-139703 [PATCH] [RFC,2/2] graph: add ip4 output fe dpdklab
2024-04-26 16:27 ` dpdklab
2024-04-26 16:28 ` dpdklab
2024-04-26 16:37 ` dpdklab
2024-04-26 16:38 ` dpdklab
2024-04-26 16:38 ` dpdklab
2024-04-26 16:40 ` dpdklab
2024-04-26 16:40 ` dpdklab
2024-04-26 16:40 ` dpdklab
2024-04-26 16:40 ` dpdklab
2024-04-26 16:41 ` dpdklab
2024-04-26 16:41 ` dpdklab
2024-04-26 16:42 ` dpdklab
2024-04-26 16:43 ` dpdklab
2024-04-26 16:43 ` dpdklab
2024-04-26 16:47 ` dpdklab
2024-04-26 16:55 ` dpdklab
2024-04-26 16:57 ` dpdklab
2024-04-26 17:02 ` dpdklab
2024-04-26 17:08 ` dpdklab
2024-04-26 17:09 ` dpdklab
2024-04-26 17:11 ` dpdklab
2024-04-26 17:12 ` dpdklab
2024-04-26 17:12 ` dpdklab
2024-04-26 17:17 ` dpdklab
2024-04-26 17:20 ` dpdklab
2024-04-26 17:22 ` dpdklab
2024-04-26 17:27 ` dpdklab
2024-04-26 17:27 ` dpdklab
2024-04-26 17:30 ` dpdklab
2024-04-26 17:31 ` dpdklab
2024-04-26 17:32 ` dpdklab
2024-04-26 17:32 ` dpdklab
2024-04-26 17:33 ` dpdklab
2024-04-26 17:35 ` dpdklab
2024-04-26 17:35 ` dpdklab
2024-04-26 17:36 ` dpdklab
2024-04-26 17:37 ` dpdklab
2024-04-26 17:38 ` dpdklab
2024-04-26 17:38 ` dpdklab
2024-04-26 17:39 ` dpdklab
2024-04-26 17:39 ` dpdklab
2024-04-26 17:40 ` dpdklab
2024-04-26 17:40 ` dpdklab
2024-04-26 17:40 ` dpdklab
2024-04-26 17:41 ` dpdklab
2024-04-26 17:41 ` dpdklab
2024-04-26 17:41 ` dpdklab
2024-04-26 17:42 ` dpdklab
2024-04-26 17:42 ` dpdklab
2024-04-26 17:43 ` dpdklab
2024-04-26 17:43 ` dpdklab
2024-04-26 17:44 ` dpdklab
2024-04-26 17:44 ` dpdklab
2024-04-26 17:45 ` dpdklab
2024-04-26 17:46 ` dpdklab
2024-04-26 17:46 ` dpdklab
2024-04-26 17:47 ` dpdklab
2024-04-26 17:49 ` |FAILURE| " dpdklab
2024-04-26 17:50 ` |SUCCESS| " dpdklab
2024-04-26 17:52 ` |FAILURE| " dpdklab
2024-04-26 17:53 ` |SUCCESS| " dpdklab
2024-04-26 17:53 ` |FAILURE| " dpdklab
2024-04-26 17:54 ` |SUCCESS| " dpdklab
2024-04-26 17:55 ` |FAILURE| " dpdklab
2024-04-26 17:55 ` |SUCCESS| " dpdklab
2024-04-26 17:56 ` |FAILURE| " dpdklab
2024-04-26 17:57 ` dpdklab
2024-04-26 17:58 ` |SUCCESS| " dpdklab
2024-04-26 17:58 ` |FAILURE| " dpdklab
2024-04-26 17:58 ` |SUCCESS| " dpdklab
2024-04-26 17:59 ` |FAILURE| " dpdklab
2024-04-26 18:00 ` dpdklab
2024-04-26 18:00 ` dpdklab
2024-04-26 18:01 ` dpdklab
2024-04-26 18:01 ` dpdklab
2024-04-26 18:02 ` |SUCCESS| " dpdklab
2024-04-26 18:02 ` |FAILURE| " dpdklab
2024-04-26 18:07 ` |SUCCESS| " dpdklab
2024-04-26 18:07 ` dpdklab
2024-04-26 18:10 ` |FAILURE| " dpdklab
2024-04-26 18:28 ` dpdklab
2024-04-26 18:37 ` |SUCCESS| " dpdklab
2024-04-26 19:12 ` |FAILURE| " dpdklab
2024-04-26 19:12 ` dpdklab
2024-04-26 19:14 ` |SUCCESS| " dpdklab
2024-04-26 19:50 ` 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=202404261158.43QBw0sD2437135@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).