automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139960-139961 [PATCH 2/2] latencystats: replace use of VLA
Date: Tue, 7 May 2024 10:28:40 +0800	[thread overview]
Message-ID: <202405070228.4472SeTK1836318@localhost.localdomain> (raw)
In-Reply-To: <20240507025355.7145-2-stephen@networkplumber.org>

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

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon,  6 May 2024 19:53:54 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

139960-139961 --> 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-05-07  2:56 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240507025355.7145-2-stephen@networkplumber.org>
2024-05-07  2:28 ` qemudev [this message]
2024-05-07  2:33 ` qemudev
2024-05-07  2:55 ` |SUCCESS| pw139961 " checkpatch
2024-05-07  3:33 ` |SUCCESS| pw139960-139961 [PATCH] [2/2] latencystats: replace use of dpdklab
2024-05-07  3:33 ` dpdklab
2024-05-07  3:33 ` dpdklab
2024-05-07  3:34 ` dpdklab
2024-05-07  3:34 ` dpdklab
2024-05-07  3:34 ` dpdklab
2024-05-07  3:34 ` dpdklab
2024-05-07  3:34 ` dpdklab
2024-05-07  3:34 ` dpdklab
2024-05-07  3:34 ` dpdklab
2024-05-07  3:35 ` dpdklab
2024-05-07  3:35 ` dpdklab
2024-05-07  3:35 ` dpdklab
2024-05-07  3:35 ` dpdklab
2024-05-07  3:36 ` dpdklab
2024-05-07  3:36 ` dpdklab
2024-05-07  3:36 ` dpdklab
2024-05-07  3:36 ` dpdklab
2024-05-07  3:36 ` dpdklab
2024-05-07  3:36 ` dpdklab
2024-05-07  3:36 ` dpdklab
2024-05-07  3:36 ` dpdklab
2024-05-07  3:37 ` dpdklab
2024-05-07  3:37 ` dpdklab
2024-05-07  3:37 ` dpdklab
2024-05-07  3:37 ` dpdklab
2024-05-07  3:38 ` dpdklab
2024-05-07  3:38 ` dpdklab
2024-05-07  3:39 ` dpdklab
2024-05-07  3:40 ` dpdklab
2024-05-07  3:41 ` dpdklab
2024-05-07  3:42 ` dpdklab
2024-05-07  3:43 ` |SUCCESS| pw139961 [PATCH 2/2] latencystats: replace use of VLA 0-day Robot
2024-05-07  3:46 ` |SUCCESS| pw139960-139961 [PATCH] [2/2] latencystats: replace use of dpdklab
2024-05-07  3:49 ` dpdklab
2024-05-07  3:49 ` dpdklab
2024-05-07  3:50 ` dpdklab
2024-05-07  3:50 ` dpdklab
2024-05-07  3:50 ` dpdklab
2024-05-07  3:51 ` dpdklab
2024-05-07  3:51 ` dpdklab
2024-05-07  3:52 ` dpdklab
2024-05-07  3:53 ` dpdklab
2024-05-07  3:53 ` dpdklab
2024-05-07  3:53 ` dpdklab
2024-05-07  3:54 ` dpdklab
2024-05-07  3:54 ` dpdklab
2024-05-07  3:54 ` dpdklab
2024-05-07  3:58 ` dpdklab
2024-05-07  4:05 ` dpdklab
2024-05-07  4:07 ` dpdklab
2024-05-07  4:17 ` dpdklab
2024-05-07  4:18 ` dpdklab
2024-05-07  4:18 ` dpdklab
2024-05-07  4:18 ` dpdklab
2024-05-07  4:19 ` dpdklab
2024-05-07  4:19 ` dpdklab
2024-05-07  4:19 ` dpdklab
2024-05-07  4:20 ` dpdklab
2024-05-07  4:21 ` dpdklab
2024-05-07  4:21 ` dpdklab
2024-05-07  4:22 ` dpdklab
2024-05-07  4:22 ` dpdklab
2024-05-07  4:22 ` dpdklab
2024-05-07  4:23 ` dpdklab
2024-05-07  4:25 ` dpdklab
2024-05-07  4:30 ` dpdklab
2024-05-07  4:41 ` dpdklab
2024-05-07  4:42 ` dpdklab
2024-05-07  4:43 ` dpdklab
2024-05-07  4:44 ` dpdklab
2024-05-07  4:45 ` dpdklab
2024-05-07  4:45 ` dpdklab
2024-05-07  4:47 ` dpdklab
2024-05-07  4:48 ` dpdklab
2024-05-07  4:49 ` dpdklab
2024-05-07  4:49 ` dpdklab
2024-05-07  4:50 ` dpdklab
2024-05-07  4:50 ` dpdklab
2024-05-07  4:50 ` dpdklab
2024-05-07  5:03 ` dpdklab
2024-05-07  5:09 ` dpdklab
2024-05-07  6:25 ` dpdklab
2024-05-07 17:37 ` 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=202405070228.4472SeTK1836318@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).