automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143063 [PATCH v5 1/1] examples/l2fwd-jobstats: fix lock availability
Date: Sun, 11 Aug 2024 23:47:11 +0800	[thread overview]
Message-ID: <202408111547.47BFlBEN251350@localhost.localdomain> (raw)
In-Reply-To: <20240811155957.576645-1-rkudurumalla@marvell.com>

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

_Compilation OK_

Submitter: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Date: Sun, 11 Aug 2024 21:29:57 +0530
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: cb9187bc5c2b4bab0ad80194ac3b60491de14e8c

143063 --> 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-11 16:16 UTC|newest]

Thread overview: 98+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240811155957.576645-1-rkudurumalla@marvell.com>
2024-08-11 15:47 ` qemudev [this message]
2024-08-11 15:51 ` qemudev
2024-08-11 16:00 ` checkpatch
2024-08-11 16:27 ` |SUCCESS| pw143063 [PATCH] [v5,1/1] examples/l2fwd-jobstats: fix loc dpdklab
2024-08-11 16:28 ` |PENDING| " dpdklab
2024-08-11 16:29 ` dpdklab
2024-08-11 16:29 ` dpdklab
2024-08-11 16:29 ` dpdklab
2024-08-11 16:30 ` dpdklab
2024-08-11 16:30 ` |SUCCESS| " dpdklab
2024-08-11 16:30 ` |PENDING| " dpdklab
2024-08-11 16:31 ` dpdklab
2024-08-11 16:31 ` dpdklab
2024-08-11 16:31 ` |SUCCESS| " dpdklab
2024-08-11 16:33 ` dpdklab
2024-08-11 16:35 ` |PENDING| " dpdklab
2024-08-11 16:35 ` |SUCCESS| " dpdklab
2024-08-11 16:35 ` |PENDING| " dpdklab
2024-08-11 16:36 ` |SUCCESS| " dpdklab
2024-08-11 16:37 ` |PENDING| " dpdklab
2024-08-11 16:37 ` dpdklab
2024-08-11 16:37 ` |SUCCESS| " dpdklab
2024-08-11 16:37 ` |PENDING| " dpdklab
2024-08-11 16:37 ` dpdklab
2024-08-11 16:37 ` dpdklab
2024-08-11 16:38 ` |SUCCESS| " dpdklab
2024-08-11 16:38 ` |PENDING| " dpdklab
2024-08-11 16:38 ` dpdklab
2024-08-11 16:41 ` |SUCCESS| " dpdklab
2024-08-11 16:42 ` |PENDING| " dpdklab
2024-08-11 16:45 ` dpdklab
2024-08-11 16:45 ` dpdklab
2024-08-11 16:46 ` dpdklab
2024-08-11 16:46 ` dpdklab
2024-08-11 16:47 ` dpdklab
2024-08-11 16:47 ` dpdklab
2024-08-11 16:48 ` dpdklab
2024-08-11 16:48 ` dpdklab
2024-08-11 16:48 ` dpdklab
2024-08-11 16:48 ` dpdklab
2024-08-11 16:48 ` |SUCCESS| " dpdklab
2024-08-11 16:49 ` |PENDING| " dpdklab
2024-08-11 16:49 ` dpdklab
2024-08-11 16:49 ` dpdklab
2024-08-11 16:51 ` dpdklab
2024-08-11 16:51 ` |SUCCESS| " dpdklab
2024-08-11 16:52 ` |PENDING| " dpdklab
2024-08-11 16:54 ` dpdklab
2024-08-11 16:55 ` dpdklab
2024-08-11 16:55 ` dpdklab
2024-08-11 16:55 ` |SUCCESS| " dpdklab
2024-08-11 16:55 ` |PENDING| " dpdklab
2024-08-11 16:56 ` dpdklab
2024-08-11 16:56 ` dpdklab
2024-08-11 16:56 ` dpdklab
2024-08-11 16:56 ` dpdklab
2024-08-11 16:56 ` dpdklab
2024-08-11 16:57 ` dpdklab
2024-08-11 16:58 ` dpdklab
2024-08-11 16:58 ` dpdklab
2024-08-11 16:59 ` dpdklab
2024-08-11 16:59 ` dpdklab
2024-08-11 17:00 ` dpdklab
2024-08-11 17:00 ` |SUCCESS| " dpdklab
2024-08-11 17:02 ` |PENDING| " dpdklab
2024-08-11 17:02 ` |SUCCESS| pw143063 [PATCH v5 1/1] examples/l2fwd-jobstats: fix lock availability 0-day Robot
2024-08-11 17:04 ` |PENDING| pw143063 [PATCH] [v5,1/1] examples/l2fwd-jobstats: fix loc dpdklab
2024-08-11 17:05 ` dpdklab
2024-08-11 17:05 ` dpdklab
2024-08-11 17:06 ` dpdklab
2024-08-11 17:07 ` dpdklab
2024-08-11 17:08 ` |SUCCESS| " dpdklab
2024-08-11 17:08 ` |PENDING| " dpdklab
2024-08-11 17:09 ` dpdklab
2024-08-11 17:11 ` dpdklab
2024-08-11 17:11 ` dpdklab
2024-08-11 17:12 ` |SUCCESS| " dpdklab
2024-08-11 17:13 ` |PENDING| " dpdklab
2024-08-11 17:13 ` dpdklab
2024-08-11 17:13 ` dpdklab
2024-08-11 17:16 ` dpdklab
2024-08-11 17:16 ` dpdklab
2024-08-11 17:18 ` dpdklab
2024-08-11 17:18 ` dpdklab
2024-08-11 17:19 ` dpdklab
2024-08-11 17:19 ` |SUCCESS| " dpdklab
2024-08-11 17:20 ` |PENDING| " dpdklab
2024-08-11 17:21 ` |SUCCESS| " dpdklab
2024-08-11 17:22 ` |PENDING| " dpdklab
2024-08-11 17:24 ` dpdklab
2024-08-11 17:25 ` dpdklab
2024-08-11 17:26 ` dpdklab
2024-08-11 17:30 ` dpdklab
2024-08-11 17:31 ` dpdklab
2024-08-11 17:31 ` |SUCCESS| " dpdklab
2024-08-11 17:47 ` |PENDING| " dpdklab
2024-08-11 17:58 ` dpdklab
2024-08-11 18:05 ` |SUCCESS| " 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=202408111547.47BFlBEN251350@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).