automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121214-121215 [PATCH v2 2/2] app/test-flow-perf: fix division or module by zero
Date: Wed, 21 Dec 2022 21:25:23 +0800	[thread overview]
Message-ID: <202212211325.2BLDPNtT2271275@localhost.localdomain> (raw)
In-Reply-To: <20221219083402.1899934-2-mahmad@marvell.com>

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

_Compilation OK_

Submitter: Mohammad Iqbal Ahmad <mahmad@marvell.com>
Date: Mon, 19 Dec 2022 14:04:01 +0530
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: c581c49cd3fcaff596fbe566e270b442e6326c79

121214-121215 --> 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:[~2022-12-21 13:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221219083402.1899934-2-mahmad@marvell.com>
2022-12-21 10:20 ` |WARNING| pw121215 " checkpatch
2022-12-21 13:25 ` qemudev [this message]
2022-12-21 13:29 ` |SUCCESS| pw121214-121215 " qemudev
2022-12-21 23:09 |SUCCESS| pw121214-121215 [PATCH] [v2, " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2022-12-21 22:32 dpdklab
2022-12-21 21:11 dpdklab
2022-12-21 21:11 dpdklab
2022-12-21 21:06 dpdklab
2022-12-21 21:05 dpdklab
2022-12-21 21:03 dpdklab
2022-12-21 21:02 dpdklab
2022-12-21 21:02 dpdklab
2022-12-21 21:02 dpdklab
2022-12-21 21:01 dpdklab
2022-12-21 21:01 dpdklab
2022-12-21 21:01 dpdklab
2022-12-21 14:56 dpdklab
2022-12-21 12:22 dpdklab
2022-12-21 12:05 dpdklab
2022-12-21 12:01 dpdklab
2022-12-21 11:58 dpdklab
2022-12-21 11:26 dpdklab
2022-12-21 11:20 dpdklab
2022-12-21 11:11 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=202212211325.2BLDPNtT2271275@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).