automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw151472-151478 [PATCH v7 7/7] test: update to latencystats tests
Date: Fri, 14 Feb 2025 04:49:24 +0800	[thread overview]
Message-ID: <202502132049.51DKnO7X1308505@localhost.localdomain> (raw)
In-Reply-To: <20250213212151.1693506-8-stephen@networkplumber.org>

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

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu, 13 Feb 2025 13:20:30 -0800
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: e5176f23ae8b31437c3e5eb875c81f95bf3a9942

151472-151478 --> 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:[~2025-02-13 21:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250213212151.1693506-8-stephen@networkplumber.org>
2025-02-13 20:49 ` qemudev [this message]
2025-02-13 20:53 ` qemudev
2025-02-13 21:23 ` |SUCCESS| pw151478 " checkpatch
2025-02-13 22:10 ` |SUCCESS| pw151472-151478 [PATCH] [v7,7/7] test: update to latencyst dpdklab
2025-02-13 22:16 ` |PENDING| " dpdklab
2025-02-13 22:20 ` |SUCCESS| " dpdklab
2025-02-13 22:22 ` dpdklab
2025-02-13 22:32 ` dpdklab
2025-02-13 22:39 ` dpdklab
2025-02-13 22:44 ` |SUCCESS| pw151478 [PATCH v7 7/7] test: update to latencystats tests 0-day Robot
2025-02-13 22:53 ` |SUCCESS| pw151472-151478 [PATCH] [v7,7/7] test: update to latencyst dpdklab
2025-02-14  3:19 ` dpdklab
2025-02-18 15:09 ` dpdklab
2025-02-18 15:26 ` 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=202502132049.51DKnO7X1308505@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).