automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139295 [PATCH] app/testpmd: fix lcore ID restriction
Date: Tue, 16 Apr 2024 03:23:09 +0800	[thread overview]
Message-ID: <202404151923.43FJN9HU3959263@localhost.localdomain> (raw)
In-Reply-To: <20240415194631.124343-1-sivaprasad.tummala@amd.com>

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

_Compilation OK_

Submitter: Sivaprasad Tummala <Sivaprasad.Tummala@amd.com>
Date: Mon, 15 Apr 2024 19:46:31 +0000
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 6db5f91b5e628671c341b833f21ea35e65e9699d

139295 --> 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-04-15 19:48 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240415194631.124343-1-sivaprasad.tummala@amd.com>
2024-04-15 19:23 ` qemudev [this message]
2024-04-15 19:27 ` qemudev
2024-04-15 19:47 ` checkpatch
2024-04-15 20:35 ` dpdklab
2024-04-15 20:36 ` |FAILURE| " dpdklab
2024-04-15 20:36 ` dpdklab
2024-04-15 20:37 ` dpdklab
2024-04-15 20:37 ` dpdklab
2024-04-15 20:37 ` dpdklab
2024-04-15 20:38 ` |SUCCESS| " dpdklab
2024-04-15 20:38 ` dpdklab
2024-04-15 20:39 ` dpdklab
2024-04-15 20:40 ` |FAILURE| " dpdklab
2024-04-15 20:40 ` dpdklab
2024-04-15 20:40 ` dpdklab
2024-04-15 20:40 ` dpdklab
2024-04-15 20:41 ` |SUCCESS| " dpdklab
2024-04-15 20:41 ` dpdklab
2024-04-15 20:41 ` |FAILURE| " dpdklab
2024-04-15 20:41 ` |SUCCESS| " dpdklab
2024-04-15 20:44 ` |FAILURE| " 0-day Robot
2024-04-15 20:45 ` |SUCCESS| " dpdklab
2024-04-15 20:45 ` |FAILURE| " dpdklab
2024-04-15 20:46 ` dpdklab
2024-04-15 20:46 ` dpdklab
2024-04-15 20:46 ` dpdklab
2024-04-15 20:46 ` dpdklab
2024-04-15 20:47 ` dpdklab
2024-04-15 20:47 ` dpdklab
2024-04-15 20:47 ` dpdklab
2024-04-15 20:47 ` dpdklab
2024-04-15 20:47 ` |SUCCESS| " dpdklab
2024-04-15 20:47 ` |FAILURE| " dpdklab
2024-04-15 20:48 ` dpdklab
2024-04-15 20:48 ` dpdklab
2024-04-15 20:48 ` dpdklab
2024-04-15 20:49 ` dpdklab
2024-04-15 20:49 ` dpdklab
2024-04-15 20:49 ` dpdklab
2024-04-15 20:49 ` dpdklab
2024-04-15 20:49 ` dpdklab
2024-04-15 20:50 ` dpdklab
2024-04-15 20:50 ` dpdklab
2024-04-15 20:50 ` |SUCCESS| " dpdklab
2024-04-15 20:50 ` |WARNING| " dpdklab
2024-04-15 20:50 ` |FAILURE| " dpdklab
2024-04-15 20:51 ` dpdklab
2024-04-15 20:51 ` dpdklab
2024-04-15 20:57 ` |SUCCESS| " dpdklab
2024-04-15 20:57 ` |FAILURE| " dpdklab
2024-04-15 20:58 ` |SUCCESS| " dpdklab
2024-04-15 20:58 ` |FAILURE| " dpdklab
2024-04-15 20:58 ` |SUCCESS| " dpdklab
2024-04-15 20:59 ` dpdklab
2024-04-15 20:59 ` dpdklab
2024-04-15 20:59 ` |FAILURE| " dpdklab
2024-04-15 20:59 ` dpdklab
2024-04-15 21:00 ` |SUCCESS| " dpdklab
2024-04-15 21:00 ` dpdklab
2024-04-15 21:00 ` |FAILURE| " dpdklab
2024-04-15 21:00 ` |SUCCESS| " dpdklab
2024-04-15 21:00 ` dpdklab
2024-04-15 21:01 ` |FAILURE| " dpdklab
2024-04-15 21:01 ` dpdklab
2024-04-15 21:01 ` |SUCCESS| " dpdklab
2024-04-15 21:02 ` |FAILURE| " dpdklab
2024-04-15 21:02 ` dpdklab
2024-04-15 21:02 ` |SUCCESS| " dpdklab
2024-04-15 21:02 ` |FAILURE| " dpdklab
2024-04-15 21:03 ` dpdklab
2024-04-15 21:03 ` dpdklab
2024-04-15 21:03 ` dpdklab
2024-04-15 21:08 ` dpdklab
2024-04-15 21:09 ` dpdklab
2024-04-15 21:10 ` dpdklab
2024-04-15 21:38 ` dpdklab
2024-04-15 21:41 ` dpdklab
2024-04-15 21:44 ` |SUCCESS| " dpdklab
2024-04-15 21:50 ` |FAILURE| " dpdklab
2024-04-15 22:16 ` 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=202404151923.43FJN9HU3959263@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).