automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw142399-142401 [PATCH 3/3] examples/l3fwd: fix maximum acceptable port ID in routes
Date: Mon, 15 Jul 2024 17:49:05 +0800	[thread overview]
Message-ID: <202407150949.46F9n5Vt1985904@localhost.localdomain> (raw)
In-Reply-To: <20240715101458.645014-3-g.singh@nxp.com>

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

_Compilation OK_

Submitter: Gagandeep Singh <g.singh@nxp.com>
Date: Mon, 15 Jul 2024 15:44:56 +0530
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: fa8d2f7f28524a6c8defa3dcd94f5aa131aae084

142399-142401 --> 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-07-15 10:18 UTC|newest]

Thread overview: 112+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240715101458.645014-3-g.singh@nxp.com>
2024-07-15  9:49 ` qemudev [this message]
2024-07-15  9:53 ` qemudev
2024-07-15 10:16 ` |SUCCESS| pw142401 " checkpatch
2024-07-15 10:48 ` |PENDING| pw142399-142401 [PATCH] [3/3] examples/l3fwd: fix maximum dpdklab
2024-07-15 10:51 ` dpdklab
2024-07-15 10:51 ` |SUCCESS| " dpdklab
2024-07-15 10:55 ` |PENDING| " dpdklab
2024-07-15 10:57 ` |SUCCESS| " dpdklab
2024-07-15 10:58 ` |PENDING| " dpdklab
2024-07-15 10:58 ` dpdklab
2024-07-15 10:59 ` |SUCCESS| " dpdklab
2024-07-15 10:59 ` dpdklab
2024-07-15 10:59 ` |PENDING| " dpdklab
2024-07-15 10:59 ` |SUCCESS| " dpdklab
2024-07-15 11:00 ` |PENDING| " dpdklab
2024-07-15 11:02 ` dpdklab
2024-07-15 11:02 ` dpdklab
2024-07-15 11:03 ` |FAILURE| " dpdklab
2024-07-15 11:03 ` |SUCCESS| pw142401 [PATCH 3/3] examples/l3fwd: fix maximum acceptable port ID in routes 0-day Robot
2024-07-15 11:03 ` |FAILURE| pw142399-142401 [PATCH] [3/3] examples/l3fwd: fix maximum dpdklab
2024-07-15 11:06 ` |PENDING| " dpdklab
2024-07-15 11:06 ` |FAILURE| " dpdklab
2024-07-15 11:06 ` |PENDING| " dpdklab
2024-07-15 11:06 ` dpdklab
2024-07-15 11:07 ` dpdklab
2024-07-15 11:10 ` |SUCCESS| " dpdklab
2024-07-15 11:11 ` |PENDING| " dpdklab
2024-07-15 11:12 ` |FAILURE| " dpdklab
2024-07-15 11:13 ` dpdklab
2024-07-15 11:13 ` |SUCCESS| " dpdklab
2024-07-15 11:14 ` |PENDING| " dpdklab
2024-07-15 11:15 ` dpdklab
2024-07-15 11:15 ` dpdklab
2024-07-15 11:15 ` dpdklab
2024-07-15 11:16 ` |SUCCESS| " dpdklab
2024-07-15 11:16 ` |FAILURE| " dpdklab
2024-07-15 11:17 ` |PENDING| " dpdklab
2024-07-15 11:17 ` dpdklab
2024-07-15 11:18 ` dpdklab
2024-07-15 11:21 ` dpdklab
2024-07-15 11:22 ` |FAILURE| " dpdklab
2024-07-15 11:22 ` |PENDING| " dpdklab
2024-07-15 11:22 ` dpdklab
2024-07-15 11:22 ` dpdklab
2024-07-15 11:23 ` |FAILURE| " dpdklab
2024-07-15 11:23 ` |SUCCESS| " dpdklab
2024-07-15 11:23 ` |PENDING| " dpdklab
2024-07-15 11:24 ` dpdklab
2024-07-15 11:24 ` dpdklab
2024-07-15 11:24 ` dpdklab
2024-07-15 11:25 ` dpdklab
2024-07-15 11:26 ` dpdklab
2024-07-15 11:27 ` dpdklab
2024-07-15 11:27 ` dpdklab
2024-07-15 11:27 ` dpdklab
2024-07-15 11:27 ` |FAILURE| " dpdklab
2024-07-15 11:27 ` |PENDING| " dpdklab
2024-07-15 11:28 ` dpdklab
2024-07-15 11:28 ` dpdklab
2024-07-15 11:29 ` dpdklab
2024-07-15 11:29 ` dpdklab
2024-07-15 11:30 ` dpdklab
2024-07-15 11:31 ` dpdklab
2024-07-15 11:32 ` dpdklab
2024-07-15 11:32 ` dpdklab
2024-07-15 11:32 ` dpdklab
2024-07-15 11:34 ` dpdklab
2024-07-15 11:34 ` |SUCCESS| " dpdklab
2024-07-15 11:34 ` |PENDING| " dpdklab
2024-07-15 11:35 ` dpdklab
2024-07-15 11:35 ` dpdklab
2024-07-15 11:35 ` dpdklab
2024-07-15 11:35 ` dpdklab
2024-07-15 11:35 ` dpdklab
2024-07-15 11:36 ` dpdklab
2024-07-15 11:37 ` dpdklab
2024-07-15 11:37 ` |SUCCESS| " dpdklab
2024-07-15 11:37 ` dpdklab
2024-07-15 11:37 ` |PENDING| " dpdklab
2024-07-15 11:38 ` |FAILURE| " dpdklab
2024-07-15 11:39 ` dpdklab
2024-07-15 11:40 ` |PENDING| " dpdklab
2024-07-15 11:41 ` |FAILURE| " dpdklab
2024-07-15 11:43 ` dpdklab
2024-07-15 11:44 ` dpdklab
2024-07-15 11:44 ` |PENDING| " dpdklab
2024-07-15 11:45 ` |FAILURE| " dpdklab
2024-07-15 11:46 ` |PENDING| " dpdklab
2024-07-15 11:46 ` |FAILURE| " dpdklab
2024-07-15 11:47 ` |PENDING| " dpdklab
2024-07-15 11:48 ` dpdklab
2024-07-15 11:52 ` |FAILURE| " dpdklab
2024-07-15 11:54 ` |PENDING| " dpdklab
2024-07-15 11:56 ` dpdklab
2024-07-15 11:57 ` dpdklab
2024-07-15 11:57 ` |FAILURE| " dpdklab
2024-07-15 11:57 ` |PENDING| " dpdklab
2024-07-15 12:00 ` dpdklab
2024-07-15 12:00 ` |FAILURE| " dpdklab
2024-07-15 12:04 ` |PENDING| " dpdklab
2024-07-15 12:05 ` dpdklab
2024-07-15 12:16 ` |SUCCESS| " dpdklab
2024-07-15 12:17 ` |PENDING| " dpdklab
2024-07-15 12:28 ` dpdklab
2024-07-15 12:36 ` dpdklab
2024-07-15 12:54 ` |SUCCESS| " dpdklab
2024-07-15 12:55 ` dpdklab
2024-07-16  7:08 ` dpdklab
2024-07-16  7:12 ` dpdklab
2024-07-16  7:16 ` dpdklab
2024-07-16  7:20 ` dpdklab
2024-07-16  7: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=202407150949.46F9n5Vt1985904@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).