automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw140956 [PATCH v1] net/mlx5: error cqe handle Tx queue need assert
Date: Wed, 12 Jun 2024 04:04:50 -0400	[thread overview]
Message-ID: <20240612080450.1667901-1-robot@bytheb.org> (raw)
In-Reply-To: <1718175943-3586-1-git-send-email-junwang01@cestc.cn>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/140956/

_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/9478465031

  parent reply	other threads:[~2024-06-12  8:04 UTC|newest]

Thread overview: 110+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1718175943-3586-1-git-send-email-junwang01@cestc.cn>
2024-06-12  6:39 ` qemudev
2024-06-12  6:44 ` qemudev
2024-06-12  7:06 ` checkpatch
2024-06-12  8:04 ` 0-day Robot [this message]
2024-06-12 10:06 ` |SUCCESS| pw140956 [PATCH] [v1] net/mlx5: error cqe handle Tx queue dpdklab
2024-06-12 10:11 ` dpdklab
2024-06-12 10:13 ` dpdklab
2024-06-12 10:15 ` dpdklab
2024-06-12 10:24 ` dpdklab
2024-06-12 10:46 ` dpdklab
2024-06-13  4:02 ` dpdklab
2024-06-13  4:04 ` dpdklab
2024-06-13  4:05 ` dpdklab
2024-06-13  4:05 ` dpdklab
2024-06-13  4:05 ` dpdklab
2024-06-13  4:06 ` dpdklab
2024-06-13  4:07 ` dpdklab
2024-06-13  4:07 ` dpdklab
2024-06-13  4:08 ` dpdklab
2024-06-13  4:08 ` dpdklab
2024-06-13  4:08 ` dpdklab
2024-06-13  4:08 ` dpdklab
2024-06-13  4:08 ` dpdklab
2024-06-13  4:09 ` dpdklab
2024-06-13  4:09 ` dpdklab
2024-06-13  4:09 ` dpdklab
2024-06-13  4:09 ` dpdklab
2024-06-13  4:09 ` dpdklab
2024-06-13  4:09 ` dpdklab
2024-06-13  4:10 ` dpdklab
2024-06-13  4:10 ` dpdklab
2024-06-13  4:10 ` dpdklab
2024-06-13  4:10 ` dpdklab
2024-06-13  4:10 ` dpdklab
2024-06-13  4:10 ` dpdklab
2024-06-13  4:10 ` dpdklab
2024-06-13  4:11 ` dpdklab
2024-06-13  4:12 ` dpdklab
2024-06-13  4:12 ` dpdklab
2024-06-13  4:13 ` dpdklab
2024-06-13  4:13 ` dpdklab
2024-06-13  4:13 ` dpdklab
2024-06-13  4:13 ` dpdklab
2024-06-13  4:13 ` dpdklab
2024-06-13  4:14 ` dpdklab
2024-06-13  4:14 ` dpdklab
2024-06-13  4:15 ` dpdklab
2024-06-13  4:15 ` dpdklab
2024-06-13  4:15 ` dpdklab
2024-06-13  4:16 ` dpdklab
2024-06-13  4:16 ` dpdklab
2024-06-13  4:16 ` dpdklab
2024-06-13  4:16 ` dpdklab
2024-06-13  4:17 ` dpdklab
2024-06-13  4:17 ` dpdklab
2024-06-13  4:17 ` dpdklab
2024-06-13  4:17 ` dpdklab
2024-06-13  4:17 ` dpdklab
2024-06-13  4:17 ` dpdklab
2024-06-13  4:17 ` dpdklab
2024-06-13  4:18 ` dpdklab
2024-06-13  4:18 ` dpdklab
2024-06-13  4:18 ` dpdklab
2024-06-13  4:18 ` dpdklab
2024-06-13  4:18 ` dpdklab
2024-06-13  4:18 ` dpdklab
2024-06-13  4:19 ` dpdklab
2024-06-13  4:19 ` dpdklab
2024-06-13  4:19 ` dpdklab
2024-06-13  4:19 ` dpdklab
2024-06-13  4:19 ` dpdklab
2024-06-13  4:19 ` dpdklab
2024-06-13  4:19 ` dpdklab
2024-06-13  4:19 ` dpdklab
2024-06-13  4:19 ` dpdklab
2024-06-13  4:19 ` dpdklab
2024-06-13  4:19 ` dpdklab
2024-06-13  4:19 ` dpdklab
2024-06-13  4:20 ` dpdklab
2024-06-13  4:20 ` dpdklab
2024-06-13  4:20 ` dpdklab
2024-06-13  4:20 ` dpdklab
2024-06-13  4:20 ` dpdklab
2024-06-13  4:20 ` dpdklab
2024-06-13  4:20 ` dpdklab
2024-06-13  4:20 ` dpdklab
2024-06-13  4:20 ` dpdklab
2024-06-13  4:20 ` dpdklab
2024-06-13  4:20 ` dpdklab
2024-06-13  4:20 ` dpdklab
2024-06-13  4:20 ` dpdklab
2024-06-13  4:20 ` dpdklab
2024-06-13  4:21 ` dpdklab
2024-06-13  4:21 ` dpdklab
2024-06-13  4:21 ` dpdklab
2024-06-13  4:21 ` dpdklab
2024-06-13  4:21 ` dpdklab
2024-06-13  4:21 ` dpdklab
2024-06-13  4:21 ` dpdklab
2024-06-13  4:21 ` dpdklab
2024-06-13  4:21 ` dpdklab
2024-06-13  4:22 ` dpdklab
2024-06-13  4:22 ` dpdklab
2024-06-13  4:22 ` dpdklab
2024-06-13  4:22 ` dpdklab
2024-06-13  4:22 ` dpdklab
2024-06-13  4:22 ` dpdklab
2024-06-13  4:22 ` dpdklab
2024-06-13  4:22 ` dpdklab
2024-06-13  4:22 ` 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=20240612080450.1667901-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --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).