automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw132249 [PATCH] net/vhost: report TX errors in port stats
Date: Sat, 7 Oct 2023 09:26:08 +0800	[thread overview]
Message-ID: <202310070126.3971Q8Zt825975@localhost.localdomain> (raw)
In-Reply-To: <20230930010024.34377-1-rdna@apple.com>

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

_Compilation OK_

Submitter: Andrey Ignatov <rdna@apple.com>
Date: Fri, 29 Sep 2023 18:00:24 -0700
DPDK git baseline: Repo:dpdk-next-virtio
  Branch: main
  CommitID: fbafb3676c482dab60c0b5465b47f2ea33893a36

132249 --> 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-10-07  1:47 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230930010024.34377-1-rdna@apple.com>
2023-09-30  1:58 ` 0-day Robot
2023-10-07  1:16 ` qemudev
2023-10-07  1:21 ` |FAILURE| " qemudev
2023-10-07  1:26 ` qemudev [this message]
2023-10-07  1:30 ` |SUCCESS| " qemudev
2023-09-30  3:28 dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-09-30  3:02 dpdklab
2023-09-30  2:59 dpdklab
2023-09-30  2:44 dpdklab
2023-09-30  2:41 dpdklab
2023-09-30  2:40 dpdklab
2023-09-30  2:38 dpdklab
2023-09-30  2:34 dpdklab
2023-09-30  2:30 dpdklab
2023-09-30  2:28 dpdklab
2023-09-30  2:26 dpdklab
2023-09-30  2:22 dpdklab
2023-09-30  2:22 dpdklab
2023-09-30  2:19 dpdklab
2023-09-30  2:11 dpdklab
2023-09-30  2:09 dpdklab
2023-09-30  2:09 dpdklab
2023-09-30  2:08 dpdklab
2023-09-30  2:08 dpdklab
2023-09-30  2:08 dpdklab
2023-09-30  2:08 dpdklab
2023-09-30  2:08 dpdklab
2023-09-30  2:07 dpdklab
2023-09-30  2:07 dpdklab
2023-09-30  2:07 dpdklab
2023-09-30  2:07 dpdklab
2023-09-30  2:07 dpdklab
2023-09-30  2:07 dpdklab
2023-09-30  2:05 dpdklab
2023-09-30  2:05 dpdklab
2023-09-30  2:04 dpdklab
2023-09-30  2:04 dpdklab
2023-09-30  2:03 dpdklab
2023-09-30  2:03 dpdklab
2023-09-30  2:03 dpdklab
2023-09-30  2:03 dpdklab
2023-09-30  2:02 dpdklab
2023-09-30  2:02 dpdklab
2023-09-30  2:02 dpdklab
2023-09-30  2:01 dpdklab
2023-09-30  2:01 dpdklab
2023-09-30  2:01 dpdklab
2023-09-30  2:00 dpdklab
2023-09-30  2:00 dpdklab
2023-09-30  1:59 dpdklab
2023-09-30  1:59 dpdklab
2023-09-30  1:59 dpdklab
2023-09-30  1:57 dpdklab
2023-09-30  1:02 checkpatch

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=202310070126.3971Q8Zt825975@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).