automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123049-123051 [PATCH v11 3/3] testpmd: cleanup cleanly from signal
Date: Sat, 4 Feb 2023 03:03:17 +0800	[thread overview]
Message-ID: <202302031903.313J3HAL2315930@localhost.localdomain> (raw)
In-Reply-To: <20230203191409.97567-4-stephen@networkplumber.org>

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

_Compilation OK_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Fri,  3 Feb 2023 11:14:07 -0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 74fce0da4e22931e6382d9345fb7e0ad360426f5

123049-123051 --> 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:[~2023-02-03 19:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230203191409.97567-4-stephen@networkplumber.org>
2023-02-03 19:03 ` qemudev [this message]
2023-02-03 19:07 ` qemudev
2023-02-03 19:16 ` |SUCCESS| pw123051 " checkpatch
2023-02-03 20:19 ` 0-day Robot
2023-02-05 21:03 |SUCCESS| pw123049-123051 [PATCH] [v11, " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-02-05  0:03 dpdklab
2023-02-05  0:03 dpdklab
2023-02-05  0:03 dpdklab
2023-02-05  0:02 dpdklab
2023-02-05  0:02 dpdklab
2023-02-05  0:02 dpdklab
2023-02-04 23:28 dpdklab
2023-02-03 21:36 dpdklab
2023-02-03 20:17 dpdklab
2023-02-03 20:08 dpdklab
2023-02-03 19:57 dpdklab
2023-02-03 19:52 dpdklab
2023-02-03 19:50 dpdklab
2023-02-03 19:46 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=202302031903.313J3HAL2315930@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).