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| pw142748 [PATCH] net/mlx5/hws: fix the valid bit of E-Swit
Date: Mon, 29 Jul 2024 07:46:51 -0700 (PDT)	[thread overview]
Message-ID: <66a7ab5b.050a0220.2743ca.969fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240729140655.1732360-1-bingz@nvidia.com>

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142748

_Functional Testing PASS_

Submitter: Bing Zhao <bingz@nvidia.com>
Date: Monday, July 29 2024 14:06:55 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:82c47f005b9a0a1e3a649664b7713443d18abe43

142748 --> functional testing pass

Upstream job id: Template-DTS-Pipeline#171345

Test environment and result as below:

Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps

Aggregate Results by Test Suite
+-----------------+--------+
|   Test Suite    | Result |
+=================+========+
| mtu_update      |  PASS  |
+-----------------+--------+
| unit_tests_mbuf |  PASS  |
+-----------------+--------+


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-29 14:46 UTC|newest]

Thread overview: 112+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240729140655.1732360-1-bingz@nvidia.com>
2024-07-29 13:47 ` |SUCCESS| pw142748 [PATCH] net/mlx5/hws: fix the valid bit of E-Switch owner qemudev
2024-07-29 13:52 ` qemudev
2024-07-29 14:08 ` checkpatch
2024-07-29 14:36 ` |SUCCESS| pw142748 [PATCH] net/mlx5/hws: fix the valid bit of E-Swit dpdklab
2024-07-29 14:38 ` |PENDING| " dpdklab
2024-07-29 14:38 ` dpdklab
2024-07-29 14:38 ` |SUCCESS| " dpdklab
2024-07-29 14:40 ` |PENDING| " dpdklab
2024-07-29 14:40 ` |SUCCESS| " dpdklab
2024-07-29 14:42 ` |PENDING| " dpdklab
2024-07-29 14:43 ` dpdklab
2024-07-29 14:43 ` |SUCCESS| " dpdklab
2024-07-29 14:44 ` dpdklab
2024-07-29 14:45 ` |PENDING| " dpdklab
2024-07-29 14:45 ` dpdklab
2024-07-29 14:45 ` dpdklab
2024-07-29 14:46 ` dpdklab
2024-07-29 14:46 ` dpdklab [this message]
2024-07-29 14:46 ` dpdklab
2024-07-29 14:47 ` dpdklab
2024-07-29 14:48 ` dpdklab
2024-07-29 14:48 ` |SUCCESS| " dpdklab
2024-07-29 14:48 ` dpdklab
2024-07-29 14:49 ` |PENDING| " dpdklab
2024-07-29 14:51 ` dpdklab
2024-07-29 14:51 ` dpdklab
2024-07-29 14:52 ` dpdklab
2024-07-29 14:55 ` |SUCCESS| " dpdklab
2024-07-29 14:57 ` |PENDING| " dpdklab
2024-07-29 14:58 ` |SUCCESS| " dpdklab
2024-07-29 14:59 ` |PENDING| " dpdklab
2024-07-29 15:00 ` dpdklab
2024-07-29 15:00 ` dpdklab
2024-07-29 15:00 ` dpdklab
2024-07-29 15:01 ` dpdklab
2024-07-29 15:01 ` |SUCCESS| " dpdklab
2024-07-29 15:02 ` |PENDING| " dpdklab
2024-07-29 15:02 ` |SUCCESS| pw142748 [PATCH] net/mlx5/hws: fix the valid bit of E-Switch owner 0-day Robot
2024-07-29 15:03 ` |PENDING| pw142748 [PATCH] net/mlx5/hws: fix the valid bit of E-Swit dpdklab
2024-07-29 15:04 ` dpdklab
2024-07-29 15:04 ` dpdklab
2024-07-29 15:04 ` dpdklab
2024-07-29 15:04 ` |SUCCESS| " dpdklab
2024-07-29 15:05 ` |PENDING| " dpdklab
2024-07-29 15:05 ` dpdklab
2024-07-29 15:06 ` dpdklab
2024-07-29 15:07 ` dpdklab
2024-07-29 15:07 ` dpdklab
2024-07-29 15:07 ` dpdklab
2024-07-29 15:08 ` dpdklab
2024-07-29 15:08 ` dpdklab
2024-07-29 15:09 ` dpdklab
2024-07-29 15:10 ` dpdklab
2024-07-29 15:13 ` dpdklab
2024-07-29 15:14 ` dpdklab
2024-07-29 15:15 ` dpdklab
2024-07-29 15:15 ` dpdklab
2024-07-29 15:15 ` dpdklab
2024-07-29 15:15 ` dpdklab
2024-07-29 15:15 ` dpdklab
2024-07-29 15:15 ` dpdklab
2024-07-29 15:16 ` dpdklab
2024-07-29 15:16 ` dpdklab
2024-07-29 15:16 ` dpdklab
2024-07-29 15:17 ` dpdklab
2024-07-29 15:17 ` dpdklab
2024-07-29 15:17 ` dpdklab
2024-07-29 15:17 ` dpdklab
2024-07-29 15:18 ` dpdklab
2024-07-29 15:18 ` dpdklab
2024-07-29 15:20 ` dpdklab
2024-07-29 15:21 ` dpdklab
2024-07-29 15:21 ` dpdklab
2024-07-29 15:22 ` dpdklab
2024-07-29 15:23 ` dpdklab
2024-07-29 15:23 ` dpdklab
2024-07-29 15:23 ` |SUCCESS| " dpdklab
2024-07-29 15:24 ` |PENDING| " dpdklab
2024-07-29 15:24 ` dpdklab
2024-07-29 15:25 ` dpdklab
2024-07-29 15:25 ` dpdklab
2024-07-29 15:25 ` |SUCCESS| " dpdklab
2024-07-29 15:25 ` dpdklab
2024-07-29 15:25 ` |PENDING| " dpdklab
2024-07-29 15:25 ` |SUCCESS| " dpdklab
2024-07-29 15:26 ` |PENDING| " dpdklab
2024-07-29 15:26 ` dpdklab
2024-07-29 15:28 ` dpdklab
2024-07-29 15:29 ` |SUCCESS| " dpdklab
2024-07-29 15:29 ` |PENDING| " dpdklab
2024-07-29 15:29 ` |SUCCESS| " dpdklab
2024-07-29 15:30 ` dpdklab
2024-07-29 15:32 ` |PENDING| " dpdklab
2024-07-29 15:33 ` |SUCCESS| " dpdklab
2024-07-29 15:35 ` |PENDING| " dpdklab
2024-07-29 15:38 ` dpdklab
2024-07-29 15:38 ` dpdklab
2024-07-29 15:38 ` dpdklab
2024-07-29 15:38 ` |SUCCESS| " dpdklab
2024-07-29 15:38 ` |PENDING| " dpdklab
2024-07-29 15:41 ` dpdklab
2024-07-29 15:43 ` dpdklab
2024-07-29 15:44 ` dpdklab
2024-07-29 15:44 ` dpdklab
2024-07-29 15:53 ` dpdklab
2024-07-29 15:54 ` dpdklab
2024-07-29 15:57 ` dpdklab
2024-07-29 16:15 ` dpdklab
2024-07-29 16:18 ` |SUCCESS| " dpdklab
2024-07-29 16:34 ` |PENDING| " dpdklab
2024-07-29 16:45 ` dpdklab
2024-07-29 16:47 ` |SUCCESS| " 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=66a7ab5b.050a0220.2743ca.969fSMTPIN_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).