automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138771-138784 [PATCH v12 14/14] maintainers: add for log library
Date: Tue, 26 Mar 2024 04:34:05 +0800	[thread overview]
Message-ID: <202403252034.42PKY5a52622669@localhost.localdomain> (raw)
In-Reply-To: <20240325205405.669897-15-stephen@networkplumber.org>

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

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon, 25 Mar 2024 13:46:58 -0700
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 0b82b5139fefe6eb5ec1a0b489fd193e8a99ab73

138771-138784 --> 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-25 20:59 UTC|newest]

Thread overview: 81+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240325205405.669897-15-stephen@networkplumber.org>
2024-03-25 20:34 ` qemudev [this message]
2024-03-25 20:38 ` |FAILURE| " qemudev
2024-03-25 20:56 ` |SUCCESS| pw138784 " checkpatch
2024-03-25 21:37 ` |FAILURE| pw138771-138784 [PATCH] [v12,14/14] maintainers: add for l dpdklab
2024-03-25 21:37 ` dpdklab
2024-03-25 21:37 ` dpdklab
2024-03-25 21:37 ` dpdklab
2024-03-25 21:38 ` |SUCCESS| " dpdklab
2024-03-25 21:38 ` dpdklab
2024-03-25 21:38 ` |FAILURE| " dpdklab
2024-03-25 21:38 ` dpdklab
2024-03-25 21:38 ` dpdklab
2024-03-25 21:38 ` dpdklab
2024-03-25 21:39 ` dpdklab
2024-03-25 21:39 ` dpdklab
2024-03-25 21:39 ` |SUCCESS| " dpdklab
2024-03-25 21:39 ` |FAILURE| " dpdklab
2024-03-25 21:39 ` dpdklab
2024-03-25 21:39 ` dpdklab
2024-03-25 21:40 ` |SUCCESS| " dpdklab
2024-03-25 21:40 ` |FAILURE| " dpdklab
2024-03-25 21:40 ` dpdklab
2024-03-25 21:40 ` dpdklab
2024-03-25 21:40 ` |SUCCESS| " dpdklab
2024-03-25 21:40 ` |FAILURE| " dpdklab
2024-03-25 21:41 ` dpdklab
2024-03-25 21:41 ` dpdklab
2024-03-25 21:41 ` |SUCCESS| " dpdklab
2024-03-25 21:41 ` |FAILURE| " dpdklab
2024-03-25 21:41 ` dpdklab
2024-03-25 21:41 ` dpdklab
2024-03-25 21:42 ` dpdklab
2024-03-25 21:42 ` dpdklab
2024-03-25 21:42 ` dpdklab
2024-03-25 21:42 ` |SUCCESS| " dpdklab
2024-03-25 21:42 ` |WARNING| " dpdklab
2024-03-25 21:42 ` |FAILURE| " dpdklab
2024-03-25 21:43 ` |SUCCESS| " dpdklab
2024-03-25 21:43 ` |FAILURE| " dpdklab
2024-03-25 21:43 ` dpdklab
2024-03-25 21:43 ` dpdklab
2024-03-25 21:43 ` dpdklab
2024-03-25 21:44 ` dpdklab
2024-03-25 21:44 ` dpdklab
2024-03-25 21:44 ` dpdklab
2024-03-25 21:44 ` |FAILURE| pw138784 [PATCH v12 14/14] maintainers: add for log library 0-day Robot
2024-03-25 21:44 ` |FAILURE| pw138771-138784 [PATCH] [v12,14/14] maintainers: add for l dpdklab
2024-03-25 21:44 ` dpdklab
2024-03-25 21:44 ` |SUCCESS| " dpdklab
2024-03-25 21:45 ` |FAILURE| " dpdklab
2024-03-25 21:45 ` dpdklab
2024-03-25 21:46 ` |SUCCESS| " dpdklab
2024-03-25 21:46 ` |FAILURE| " dpdklab
2024-03-25 21:46 ` |SUCCESS| " dpdklab
2024-03-25 21:47 ` dpdklab
2024-03-25 21:47 ` |FAILURE| " dpdklab
2024-03-25 21:47 ` |SUCCESS| " dpdklab
2024-03-25 21:47 ` |FAILURE| " dpdklab
2024-03-25 21:48 ` dpdklab
2024-03-25 21:48 ` dpdklab
2024-03-25 21:49 ` dpdklab
2024-03-25 21:49 ` dpdklab
2024-03-25 21:50 ` |SUCCESS| " dpdklab
2024-03-25 21:50 ` dpdklab
2024-03-25 21:51 ` dpdklab
2024-03-25 21:51 ` |FAILURE| " dpdklab
2024-03-25 21:51 ` dpdklab
2024-03-25 21:52 ` dpdklab
2024-03-25 21:53 ` |SUCCESS| " dpdklab
2024-03-25 21:54 ` dpdklab
2024-03-25 21:55 ` |FAILURE| " dpdklab
2024-03-25 22:01 ` dpdklab
2024-03-25 22:07 ` dpdklab
2024-03-25 22:52 ` dpdklab
2024-03-25 23:16 ` |SUCCESS| " dpdklab
2024-03-25 23:56 ` dpdklab
2024-04-01 17:52 ` dpdklab
2024-04-01 17:53 ` dpdklab
2024-04-01 18:10 ` dpdklab
2024-04-01 18:29 ` dpdklab
2024-04-01 18:33 ` 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=202403252034.42PKY5a52622669@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).