automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122117-122122 [PATCH v2 6/6] test/dmadev: add tests for stopping and restarting dev
Date: Tue, 17 Jan 2023 01:32:03 +0800	[thread overview]
Message-ID: <202301161732.30GHW32r1132198@localhost.localdomain> (raw)
In-Reply-To: <20230116173738.562322-7-bruce.richardson@intel.com>

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

_Compilation OK_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Mon, 16 Jan 2023 17:37:32 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 83397b9f073904438965e1fda2efe76f7850fe01

122117-122122 --> 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-01-16 17:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230116173738.562322-7-bruce.richardson@intel.com>
2023-01-16 17:32 ` qemudev [this message]
2023-01-16 17:35 ` qemudev
2023-01-16 17:38 ` |SUCCESS| pw122122 " checkpatch
2023-01-16 18:59 ` |FAILURE| " 0-day Robot
2023-01-16 23:54 |SUCCESS| pw122117-122122 [PATCH] [v2, " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-01-16 22:58 dpdklab
2023-01-16 22:49 dpdklab
2023-01-16 22:37 dpdklab
2023-01-16 22:36 dpdklab
2023-01-16 22:21 dpdklab
2023-01-16 22:20 dpdklab
2023-01-16 22:20 dpdklab
2023-01-16 22:17 dpdklab
2023-01-16 21:15 dpdklab
2023-01-16 21:15 dpdklab
2023-01-16 19:57 dpdklab
2023-01-16 18:48 dpdklab
2023-01-16 18:39 dpdklab
2023-01-16 18:32 dpdklab
2023-01-16 18:28 dpdklab
2023-01-16 18:23 dpdklab
2023-01-16 18:20 dpdklab
2023-01-16 18:17 dpdklab
2023-01-16 18: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=202301161732.30GHW32r1132198@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).