automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137666-137672 [PATCH v4 7/7] dts: improve test suite and case filtering
Date: Sat, 2 Mar 2024 14:16:09 +0800	[thread overview]
Message-ID: <202403020616.4226G9vB3799210@localhost.localdomain> (raw)
In-Reply-To: <20240301105522.79870-8-juraj.linkes@pantheon.tech>

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

_Compilation OK_

Submitter: Juraj Linkeš <juraj.linkes@pantheon.tech>
Date: Fri,  1 Mar 2024 11:55:16 +0100
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 5df34de5808a7b826b8bc035d6ee3161a12be364

137666-137672 --> 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


  parent reply	other threads:[~2024-03-02  6:41 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240301105522.79870-8-juraj.linkes@pantheon.tech>
2024-03-01 10:58 ` |WARNING| pw137672 " checkpatch
2024-03-01 11:46 ` |SUCCESS| " 0-day Robot
2024-03-01 13:42 ` |FAILURE| pw137666-137672 [PATCH] [v4,7/7] dts: improve test suite a dpdklab
2024-03-01 13:42 ` |SUCCESS| " dpdklab
2024-03-01 14:00 ` dpdklab
2024-03-01 14:00 ` dpdklab
2024-03-01 14:16 ` dpdklab
2024-03-01 14:16 ` dpdklab
2024-03-01 14:17 ` |FAILURE| " dpdklab
2024-03-01 14:17 ` |SUCCESS| " dpdklab
2024-03-01 14:24 ` |FAILURE| " dpdklab
2024-03-01 14:24 ` |SUCCESS| " dpdklab
2024-03-01 14:25 ` dpdklab
2024-03-01 14:26 ` dpdklab
2024-03-01 14:27 ` dpdklab
2024-03-01 14:27 ` dpdklab
2024-03-01 14:28 ` dpdklab
2024-03-01 14:28 ` dpdklab
2024-03-01 14:29 ` dpdklab
2024-03-01 14:29 ` dpdklab
2024-03-01 14:33 ` dpdklab
2024-03-01 14:34 ` dpdklab
2024-03-01 14:36 ` dpdklab
2024-03-01 14:48 ` dpdklab
2024-03-01 14:48 ` dpdklab
2024-03-01 14:49 ` dpdklab
2024-03-01 14:49 ` dpdklab
2024-03-01 14:50 ` dpdklab
2024-03-01 14:52 ` dpdklab
2024-03-01 14:52 ` dpdklab
2024-03-01 14:52 ` dpdklab
2024-03-01 14:53 ` dpdklab
2024-03-01 14:54 ` dpdklab
2024-03-01 14:54 ` dpdklab
2024-03-01 14:54 ` dpdklab
2024-03-01 14:56 ` dpdklab
2024-03-01 14:59 ` dpdklab
2024-03-01 14:59 ` dpdklab
2024-03-01 14:59 ` dpdklab
2024-03-01 14:59 ` dpdklab
2024-03-01 14:59 ` dpdklab
2024-03-01 15:00 ` dpdklab
2024-03-01 15:01 ` dpdklab
2024-03-01 15:01 ` dpdklab
2024-03-01 15:01 ` dpdklab
2024-03-01 15:02 ` dpdklab
2024-03-01 15:06 ` dpdklab
2024-03-01 15:07 ` dpdklab
2024-03-01 15:08 ` dpdklab
2024-03-01 15:08 ` dpdklab
2024-03-01 15:10 ` dpdklab
2024-03-01 15:14 ` dpdklab
2024-03-01 15:14 ` dpdklab
2024-03-01 15:15 ` dpdklab
2024-03-01 15:15 ` dpdklab
2024-03-01 15:16 ` dpdklab
2024-03-01 15:17 ` dpdklab
2024-03-01 15:17 ` dpdklab
2024-03-01 15:17 ` dpdklab
2024-03-01 15:18 ` dpdklab
2024-03-01 15:22 ` dpdklab
2024-03-01 15:26 ` dpdklab
2024-03-01 15:27 ` dpdklab
2024-03-01 15:49 ` dpdklab
2024-03-01 16:08 ` dpdklab
2024-03-01 18:27 ` dpdklab
2024-03-01 18:31 ` dpdklab
2024-03-01 18:36 ` |FAILURE| " dpdklab
2024-03-01 18:38 ` |SUCCESS| " dpdklab
2024-03-01 18:57 ` |FAILURE| " dpdklab
2024-03-01 19:16 ` |SUCCESS| " dpdklab
2024-03-02  2:55 ` dpdklab
2024-03-02  2:58 ` dpdklab
2024-03-02  6:16 ` qemudev [this message]
2024-03-02  6:20 ` |SUCCESS| pw137666-137672 [PATCH v4 7/7] dts: improve test suite and case filtering qemudev
2024-03-02 17:48 ` |SUCCESS| pw137666-137672 [PATCH] [v4,7/7] dts: improve test suite a dpdklab
2024-03-02 20:03 ` dpdklab
2024-03-02 20:11 ` dpdklab
2024-03-05  2:46 ` dpdklab
2024-03-05  3:21 ` dpdklab
2024-03-05  3:52 ` 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=202403020616.4226G9vB3799210@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).