automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138827-138832 [PATCH 6/6] dts: add statefulness to TestPmdShell
Date: Wed, 27 Mar 2024 02:43:13 +0800	[thread overview]
Message-ID: <202403261843.42QIhD9S3092111@localhost.localdomain> (raw)
In-Reply-To: <20240326190422.577028-7-luca.vizzarro@arm.com>

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

_Compilation OK_

Submitter: Luca Vizzarro <luca.vizzarro@arm.com>
Date: Tue, 26 Mar 2024 19:04:17 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: ded4d4765171b88470e59307f10625e942f22fca

138827-138832 --> 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-03-26 19:08 UTC|newest]

Thread overview: 91+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240326190422.577028-7-luca.vizzarro@arm.com>
2024-03-26 18:43 ` qemudev [this message]
2024-03-26 18:47 ` qemudev
2024-03-26 19:06 ` |SUCCESS| pw138832 " checkpatch
2024-03-26 19:49 ` |SUCCESS| pw138827-138832 [PATCH] [6/6] dts: add statefulness to Tes dpdklab
2024-03-26 19:49 ` dpdklab
2024-03-26 19:49 ` dpdklab
2024-03-26 19:50 ` dpdklab
2024-03-26 19:50 ` dpdklab
2024-03-26 19:50 ` dpdklab
2024-03-26 19:51 ` dpdklab
2024-03-26 19:51 ` dpdklab
2024-03-26 19:51 ` dpdklab
2024-03-26 19:51 ` dpdklab
2024-03-26 19:52 ` dpdklab
2024-03-26 19:52 ` dpdklab
2024-03-26 19:53 ` dpdklab
2024-03-26 19:53 ` dpdklab
2024-03-26 19:53 ` dpdklab
2024-03-26 19:53 ` dpdklab
2024-03-26 19:53 ` dpdklab
2024-03-26 19:54 ` dpdklab
2024-03-26 19:54 ` dpdklab
2024-03-26 19:54 ` dpdklab
2024-03-26 19:55 ` dpdklab
2024-03-26 19:55 ` dpdklab
2024-03-26 19:55 ` dpdklab
2024-03-26 19:56 ` dpdklab
2024-03-26 19:56 ` dpdklab
2024-03-26 19:56 ` dpdklab
2024-03-26 19:56 ` dpdklab
2024-03-26 19:56 ` dpdklab
2024-03-26 19:57 ` dpdklab
2024-03-26 19:57 ` dpdklab
2024-03-26 19:58 ` dpdklab
2024-03-26 19:58 ` dpdklab
2024-03-26 19:58 ` dpdklab
2024-03-26 19:59 ` dpdklab
2024-03-26 19:59 ` dpdklab
2024-03-26 20:00 ` dpdklab
2024-03-26 20:00 ` dpdklab
2024-03-26 20:01 ` dpdklab
2024-03-26 20:01 ` dpdklab
2024-03-26 20:02 ` dpdklab
2024-03-26 20:02 ` dpdklab
2024-03-26 20:02 ` dpdklab
2024-03-26 20:03 ` dpdklab
2024-03-26 20:03 ` dpdklab
2024-03-26 20:03 ` dpdklab
2024-03-26 20:03 ` dpdklab
2024-03-26 20:04 ` dpdklab
2024-03-26 20:04 ` dpdklab
2024-03-26 20:04 ` dpdklab
2024-03-26 20:04 ` |SUCCESS| pw138832 [PATCH 6/6] dts: add statefulness to TestPmdShell 0-day Robot
2024-03-26 20:05 ` |SUCCESS| pw138827-138832 [PATCH] [6/6] dts: add statefulness to Tes dpdklab
2024-03-26 20:05 ` dpdklab
2024-03-26 20:07 ` dpdklab
2024-03-26 20:07 ` dpdklab
2024-03-26 20:08 ` dpdklab
2024-03-26 20:08 ` dpdklab
2024-03-26 20:12 ` dpdklab
2024-03-26 20:12 ` dpdklab
2024-03-26 20:12 ` dpdklab
2024-03-26 20:12 ` dpdklab
2024-03-26 20:12 ` dpdklab
2024-03-26 20:12 ` dpdklab
2024-03-26 20:14 ` dpdklab
2024-03-26 20:14 ` dpdklab
2024-03-26 20:15 ` dpdklab
2024-03-26 20:17 ` dpdklab
2024-03-26 20:18 ` dpdklab
2024-03-26 20:21 ` dpdklab
2024-03-26 20:22 ` dpdklab
2024-03-26 20:25 ` dpdklab
2024-03-26 20:25 ` dpdklab
2024-03-26 20:26 ` dpdklab
2024-03-26 20:30 ` dpdklab
2024-03-26 20:31 ` dpdklab
2024-03-26 20:33 ` dpdklab
2024-03-26 20:33 ` dpdklab
2024-03-26 20:34 ` dpdklab
2024-03-26 20:36 ` dpdklab
2024-03-26 20:44 ` dpdklab
2024-03-26 20:55 ` dpdklab
2024-03-26 21:05 ` dpdklab
2024-03-26 21:08 ` dpdklab
2024-03-26 22:31 ` dpdklab
2024-04-02  1:31 ` dpdklab
2024-04-02  1:34 ` dpdklab
2024-04-02  1:39 ` dpdklab
2024-04-02  1:58 ` dpdklab
2024-04-02  2:02 ` 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=202403261843.42QIhD9S3092111@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).