automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120482-120478 [PATCH V4 5/5] app/testpmd: stop forwarding in new or destroy event
Date: Fri, 9 Dec 2022 00:32:46 +0800	[thread overview]
Message-ID: <202212081632.2B8GWkdu196743@localhost.localdomain> (raw)
In-Reply-To: <20221206092649.8287-6-lihuisong@huawei.com>

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

_Compilation OK_

Submitter: Huisong Li <lihuisong@huawei.com>
Date: Tue, 6 Dec 2022 17:26:45 +0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 6c8aed5ab7f6dbed8e71199504fa227f5f60c6fd

120482-120478 --> 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-12 11:36 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221206092649.8287-6-lihuisong@huawei.com>
2022-12-06  9:30 ` |SUCCESS| pw120478 " checkpatch
2022-12-06 11:39 ` 0-day Robot
2022-12-08 16:32 ` qemudev [this message]
2022-12-08 16:33 ` |SUCCESS| pw120482-120478 " qemudev
2022-12-08 17:08 ` qemudev
2022-12-08 17:09 ` qemudev
2022-12-10  0:57 ` qemudev
2022-12-10  0:58 ` qemudev
2023-01-11 18:38 |SUCCESS| pw120482-120478 [PATCH] [V4, " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-01-11 18:05 dpdklab
2023-01-11 17:55 dpdklab
2023-01-11 17:54 dpdklab
2023-01-11 17:54 dpdklab
2023-01-11 17:54 dpdklab
2023-01-11 17:54 dpdklab
2023-01-11 17:54 dpdklab
2023-01-11 17:33 dpdklab
2023-01-11 17:01 dpdklab
2023-01-11 16:55 dpdklab
2023-01-11 16:55 dpdklab
2023-01-11 16:54 dpdklab
2023-01-11 16:51 dpdklab
2023-01-11 13:06 dpdklab
2023-01-11 11:28 dpdklab
2023-01-11 11:08 dpdklab
2023-01-11 10:54 dpdklab
2023-01-11 10:47 dpdklab
2023-01-11 10:32 dpdklab
2023-01-11 10:29 dpdklab
2023-01-11 10:22 dpdklab
2022-12-06 15:19 dpdklab
2022-12-06 12:23 dpdklab
2022-12-06 12:03 dpdklab
2022-12-06 12:01 dpdklab
2022-12-06 11:48 dpdklab
2022-12-06 11:48 dpdklab
2022-12-06 11:36 dpdklab
2022-12-06 11:35 dpdklab
2022-12-06 10:37 dpdklab
2022-12-06 10:29 dpdklab
2022-12-06 10:22 dpdklab
2022-12-06 10:17 dpdklab
2022-12-06 10:10 dpdklab
2022-12-06 10:01 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=202212081632.2B8GWkdu196743@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).