automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122905-122908 [PATCH v8 4/4] eal: add PMU support to tracing library
Date: Fri, 3 Feb 2023 16:21:57 +0800	[thread overview]
Message-ID: <202302030821.3138LuuA929728@localhost.localdomain> (raw)
In-Reply-To: <20230202094358.2838758-5-tduszynski@marvell.com>

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

_Compilation OK_

Submitter: Tomasz Duszynski <tduszynski@marvell.com>
Date: Thu, 2 Feb 2023 10:43:55 +0100
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: bc1db4f45af35c87e7d97db7a24d479674aa8a43

122905-122908 --> 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-02-03  8:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230202094358.2838758-5-tduszynski@marvell.com>
2023-02-02  9:45 ` |SUCCESS| pw122908 " checkpatch
2023-02-02 11:19 ` 0-day Robot
2023-02-02 11:43 ` |SUCCESS| pw122905-122908 " qemudev
2023-02-02 11:48 ` |FAILURE| " qemudev
2023-02-03  8:21 ` qemudev [this message]
2023-02-03  8:25 ` |SUCCESS| " qemudev
2023-02-04  4:04 |SUCCESS| pw122905-122908 [PATCH] [v8, " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-02-03 23:05 dpdklab
2023-02-02 17:56 dpdklab
2023-02-02 12:03 dpdklab
2023-02-02 10:49 dpdklab
2023-02-02 10:33 dpdklab
2023-02-02 10:29 dpdklab
2023-02-02 10:27 dpdklab
2023-02-02 10:25 dpdklab
2023-02-02 10:22 dpdklab
2023-02-02 10:20 dpdklab
2023-02-02 10:18 dpdklab
2023-02-02 10:12 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=202302030821.3138LuuA929728@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).