automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143688-143689 [PATCH] [3/3] net/mlx5/hws: print CQE erro
Date: Fri, 06 Sep 2024 16:57:43 -0700 (PDT)	[thread overview]
Message-ID: <66db96f7.050a0220.144a31.0c56SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240906102151.171965-4-gavinl@nvidia.com>

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143689

_Functional Testing PASS_

Submitter: Gavin Li <gavinl@nvidia.com>
Date: Friday, September 06 2024 10:21:51 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:1afebcc334d9a19f94b87062815067f77a195f76

143688-143689 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#178922

Test environment and result as below:

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps

Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter    |  PASS  |
+------------+--------+


To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30933/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-09-06 23:57 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240906102151.171965-4-gavinl@nvidia.com>
2024-09-06  9:55 ` |SUCCESS| pw143688-143689 [PATCH 3/3] net/mlx5/hws: print CQE error syndrome and more information qemudev
2024-09-06 10:00 ` qemudev
2024-09-06 10:23 ` |WARNING| pw143689 " checkpatch
2024-09-06 11:24 ` |SUCCESS| " 0-day Robot
2024-09-06 11:35 ` |PENDING| pw143688-143689 [PATCH] [3/3] net/mlx5/hws: print CQE erro dpdklab
2024-09-06 12:03 ` |SUCCESS| " dpdklab
2024-09-06 12:09 ` dpdklab
2024-09-06 13:18 ` dpdklab
2024-09-06 13:23 ` dpdklab
2024-09-06 13:47 ` |PENDING| " dpdklab
2024-09-06 14:02 ` dpdklab
2024-09-06 14:13 ` |SUCCESS| " dpdklab
2024-09-06 14:34 ` dpdklab
2024-09-06 14:36 ` dpdklab
2024-09-06 14:37 ` dpdklab
2024-09-06 14:37 ` dpdklab
2024-09-06 15:02 ` dpdklab
2024-09-06 15:08 ` |PENDING| " dpdklab
2024-09-06 15:19 ` |SUCCESS| " dpdklab
2024-09-06 15:26 ` dpdklab
2024-09-06 16:35 ` dpdklab
2024-09-06 18:41 ` |WARNING| " dpdklab
2024-09-06 19:43 ` |SUCCESS| " dpdklab
2024-09-06 19:47 ` dpdklab
2024-09-06 19:49 ` dpdklab
2024-09-06 20:01 ` dpdklab
2024-09-06 20:01 ` dpdklab
2024-09-06 21:39 ` dpdklab
2024-09-06 21:40 ` dpdklab
2024-09-06 21:47 ` dpdklab
2024-09-06 23:20 ` dpdklab
2024-09-06 23:46 ` dpdklab
2024-09-06 23:53 ` dpdklab
2024-09-06 23:57 ` dpdklab [this message]
2024-09-07  0:02 ` dpdklab
2024-09-07  0:06 ` dpdklab
2024-09-07  0:33 ` dpdklab
2024-09-07  0:56 ` dpdklab
2024-09-07  4:03 ` |PENDING| " dpdklab
2024-09-07  4:14 ` |SUCCESS| " dpdklab
2024-09-07  4:16 ` dpdklab
2024-09-07  4:42 ` dpdklab
2024-09-07  5:43 ` dpdklab
2024-09-07  7:57 ` dpdklab
2024-09-07  8:45 ` dpdklab
2024-09-07 14:46 ` dpdklab
2024-09-07 17:32 ` dpdklab
2024-09-08  0:05 ` dpdklab
2024-09-08  0:37 ` dpdklab
2024-09-17 10:06 ` dpdklab
2024-09-17 10:27 ` dpdklab
2024-09-17 10:40 ` dpdklab
2024-09-17 11: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=66db96f7.050a0220.144a31.0c56SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).