automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122429-122431 [PATCH v4 3/3] telemetry: use standard logging
Date: Wed, 25 Jan 2023 09:42:34 +0800	[thread overview]
Message-ID: <202301250142.30P1gYLl491572@localhost.localdomain> (raw)
In-Reply-To: <20230120182154.481039-4-bruce.richardson@intel.com>

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

_Compilation OK_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Fri, 20 Jan 2023 18:21:52 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 2a211079a92e962bbd0ec81e425a6ffc32890e67

122429-122431 --> 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:[~2023-01-25  1:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230120182154.481039-4-bruce.richardson@intel.com>
2023-01-20 18:22 ` |SUCCESS| pw122431 " checkpatch
2023-01-20 19:39 ` |FAILURE| " 0-day Robot
2023-01-25  1:42 ` qemudev [this message]
2023-01-25  1:43 ` |SUCCESS| pw122429-122431 " qemudev
2023-01-21 10:48 |SUCCESS| pw122429-122431 [PATCH] [v4, " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-01-21  4:10 dpdklab
2023-01-21  1:33 dpdklab
2023-01-21  1:32 dpdklab
2023-01-21  1:32 dpdklab
2023-01-21  1:32 dpdklab
2023-01-21  1:31 dpdklab
2023-01-21  1:31 dpdklab
2023-01-21  1:31 dpdklab
2023-01-21  1:31 dpdklab
2023-01-21  1:31 dpdklab
2023-01-21  1:30 dpdklab
2023-01-20 19:41 dpdklab
2023-01-20 19:10 dpdklab
2023-01-20 19:06 dpdklab
2023-01-20 18:56 dpdklab
2023-01-20 18:54 dpdklab
2023-01-20 18:50 dpdklab
2023-01-20 18:50 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=202301250142.30P1gYLl491572@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).