automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw142883-142893 [PATCH v4 11/11] doc: update nfp document
Date: Mon, 5 Aug 2024 09:48:32 +0800	[thread overview]
Message-ID: <202408050148.4751mWUQ1664093@localhost.localdomain> (raw)
In-Reply-To: <20240805021248.1051198-12-chaoyong.he@corigine.com>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/142893

_Compilation OK_

Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Mon,  5 Aug 2024 10:12:38 +0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 37ce4c84c0f23c3989bc7ae19e03a4593cec94e5

142883-142893 --> 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


       reply	other threads:[~2024-08-05  2:17 UTC|newest]

Thread overview: 110+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240805021248.1051198-12-chaoyong.he@corigine.com>
2024-08-05  1:48 ` qemudev [this message]
2024-08-05  1:52 ` qemudev
2024-08-05  2:16 ` |SUCCESS| pw142893 " checkpatch
2024-08-05  2:50 ` |SUCCESS| pw142883-142893 [PATCH] [v4,11/11] doc: update nfp documen dpdklab
2024-08-05  2:54 ` dpdklab
2024-08-05  2:55 ` dpdklab
2024-08-05  2:55 ` |PENDING| " dpdklab
2024-08-05  2:55 ` |SUCCESS| " dpdklab
2024-08-05  2:56 ` |PENDING| " dpdklab
2024-08-05  2:56 ` dpdklab
2024-08-05  2:57 ` dpdklab
2024-08-05  2:58 ` dpdklab
2024-08-05  2:59 ` |SUCCESS| " dpdklab
2024-08-05  3:00 ` |PENDING| " dpdklab
2024-08-05  3:00 ` dpdklab
2024-08-05  3:01 ` dpdklab
2024-08-05  3:01 ` |SUCCESS| " dpdklab
2024-08-05  3:02 ` |SUCCESS| pw142893 [PATCH v4 11/11] doc: update nfp document 0-day Robot
2024-08-05  3:03 ` |PENDING| pw142883-142893 [PATCH] [v4,11/11] doc: update nfp documen dpdklab
2024-08-05  3:03 ` |SUCCESS| " dpdklab
2024-08-05  3:03 ` |PENDING| " dpdklab
2024-08-05  3:04 ` dpdklab
2024-08-05  3:04 ` dpdklab
2024-08-05  3:05 ` dpdklab
2024-08-05  3:06 ` dpdklab
2024-08-05  3:07 ` dpdklab
2024-08-05  3:07 ` dpdklab
2024-08-05  3:07 ` dpdklab
2024-08-05  3:08 ` dpdklab
2024-08-05  3:08 ` dpdklab
2024-08-05  3:09 ` dpdklab
2024-08-05  3:10 ` dpdklab
2024-08-05  3:11 ` dpdklab
2024-08-05  3:11 ` dpdklab
2024-08-05  3:11 ` dpdklab
2024-08-05  3:11 ` dpdklab
2024-08-05  3:11 ` |SUCCESS| " dpdklab
2024-08-05  3:11 ` |PENDING| " dpdklab
2024-08-05  3:11 ` dpdklab
2024-08-05  3:11 ` dpdklab
2024-08-05  3:12 ` dpdklab
2024-08-05  3:12 ` dpdklab
2024-08-05  3:13 ` |SUCCESS| " dpdklab
2024-08-05  3:16 ` |PENDING| " dpdklab
2024-08-05  3:16 ` dpdklab
2024-08-05  3:16 ` dpdklab
2024-08-05  3:17 ` |SUCCESS| " dpdklab
2024-08-05  3:19 ` |PENDING| " dpdklab
2024-08-05  3:20 ` dpdklab
2024-08-05  3:21 ` dpdklab
2024-08-05  3:22 ` dpdklab
2024-08-05  3:22 ` dpdklab
2024-08-05  3:23 ` dpdklab
2024-08-05  3:23 ` dpdklab
2024-08-05  3:24 ` dpdklab
2024-08-05  3:24 ` dpdklab
2024-08-05  3:24 ` dpdklab
2024-08-05  3:27 ` dpdklab
2024-08-05  3:27 ` dpdklab
2024-08-05  3:28 ` dpdklab
2024-08-05  3:28 ` dpdklab
2024-08-05  3:34 ` dpdklab
2024-08-05  3:35 ` dpdklab
2024-08-05  3:36 ` dpdklab
2024-08-05  3:36 ` dpdklab
2024-08-05  3:37 ` dpdklab
2024-08-05  3:38 ` dpdklab
2024-08-05  3:39 ` dpdklab
2024-08-05  3:40 ` dpdklab
2024-08-05  3:41 ` dpdklab
2024-08-05  3:41 ` dpdklab
2024-08-05  3:42 ` dpdklab
2024-08-05  3:43 ` dpdklab
2024-08-05  3:43 ` |SUCCESS| " dpdklab
2024-08-05  3:45 ` |PENDING| " dpdklab
2024-08-05  3:46 ` dpdklab
2024-08-05  3:47 ` |SUCCESS| " dpdklab
2024-08-05  3:47 ` |PENDING| " dpdklab
2024-08-05  3:48 ` dpdklab
2024-08-05  3:49 ` dpdklab
2024-08-05  3:49 ` dpdklab
2024-08-05  3:50 ` dpdklab
2024-08-05  3:50 ` dpdklab
2024-08-05  3:51 ` dpdklab
2024-08-05  3:51 ` dpdklab
2024-08-05  3:52 ` dpdklab
2024-08-05  3:54 ` dpdklab
2024-08-05  3:57 ` dpdklab
2024-08-05  3:57 ` dpdklab
2024-08-05  3:58 ` |SUCCESS| " dpdklab
2024-08-05  3:59 ` |PENDING| " dpdklab
2024-08-05  4:02 ` dpdklab
2024-08-05  4:03 ` dpdklab
2024-08-05  4:04 ` |SUCCESS| " dpdklab
2024-08-05  4:06 ` dpdklab
2024-08-05  4:06 ` |PENDING| " dpdklab
2024-08-05  4:07 ` dpdklab
2024-08-05  4:10 ` dpdklab
2024-08-05  4:10 ` dpdklab
2024-08-05  4:11 ` dpdklab
2024-08-05  4:14 ` dpdklab
2024-08-05  4:15 ` dpdklab
2024-08-05  4:15 ` dpdklab
2024-08-05  4:18 ` dpdklab
2024-08-05  4:28 ` dpdklab
2024-08-05  4:33 ` |SUCCESS| " dpdklab
2024-08-05  4:42 ` dpdklab
2024-08-06 18:41 ` dpdklab
2024-08-06 18:50 ` dpdklab
2024-08-06 19:06 ` 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=202408050148.4751mWUQ1664093@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).