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| pw140731 [PATCH] net/mlx5: add queue hardware object conte
Date: Tue, 04 Jun 2024 15:53:22 -0700 (PDT)	[thread overview]
Message-ID: <665f9ae2.630a0220.b9a62.9f73SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240604211136.1616519-1-kiranv@nvidia.com>

Test-Label: iol-abi-testing
Test-Status: SUCCESS
http://dpdk.org/patch/140731

_Testing PASS_

Submitter: Kiran Vedere <kiranv@nvidia.com>
Date: Tuesday, June 04 2024 21:11:36 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:a207de9a356ef890dd858064ee94e15f0841f0e1

140731 --> testing pass

Test environment and result as below:

+-----------------+----------+
|   Environment   | abi_test |
+=================+==========+
| Debian Bullseye | PASS     |
+-----------------+----------+
| CentOS Stream 8 | PASS     |
+-----------------+----------+
| CentOS Stream 9 | PASS     |
+-----------------+----------+
| Fedora 39       | PASS     |
+-----------------+----------+
| Debian 12       | PASS     |
+-----------------+----------+
| Fedora 37       | PASS     |
+-----------------+----------+


Debian Bullseye
	Kernel: 5.4.0-167-generic
	Compiler: gcc 10.2.1-6

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

Fedora 39
	Kernel: Depends on container host
	Compiler: clang 17.0.6

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-04 22:53 UTC|newest]

Thread overview: 99+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240604211136.1616519-1-kiranv@nvidia.com>
2024-06-04 20:46 ` |SUCCESS| pw140731 [PATCH] net/mlx5: add queue hardware object context dump qemudev
2024-06-04 20:50 ` qemudev
2024-06-04 21:12 ` |WARNING| " checkpatch
2024-06-04 22:14 ` |SUCCESS| pw140731 [PATCH] net/mlx5: add queue hardware object conte dpdklab
2024-06-04 22:32 ` dpdklab
2024-06-04 22:32 ` dpdklab
2024-06-04 22:34 ` dpdklab
2024-06-04 22:34 ` dpdklab
2024-06-04 22:34 ` dpdklab
2024-06-04 22:35 ` dpdklab
2024-06-04 22:35 ` dpdklab
2024-06-04 22:35 ` dpdklab
2024-06-04 22:36 ` dpdklab
2024-06-04 22:36 ` dpdklab
2024-06-04 22:36 ` dpdklab
2024-06-04 22:37 ` dpdklab
2024-06-04 22:38 ` dpdklab
2024-06-04 22:39 ` dpdklab
2024-06-04 22:40 ` dpdklab
2024-06-04 22:41 ` dpdklab
2024-06-04 22:41 ` dpdklab
2024-06-04 22:41 ` dpdklab
2024-06-04 22:42 ` dpdklab
2024-06-04 22:53 ` dpdklab
2024-06-04 22:53 ` dpdklab [this message]
2024-06-04 22:53 ` dpdklab
2024-06-04 22:54 ` dpdklab
2024-06-04 22:54 ` dpdklab
2024-06-04 22:55 ` dpdklab
2024-06-04 23:03 ` dpdklab
2024-06-04 23:03 ` dpdklab
2024-06-04 23:03 ` dpdklab
2024-06-04 23:20 ` dpdklab
2024-06-04 23:21 ` dpdklab
2024-06-04 23:21 ` dpdklab
2024-06-04 23:21 ` dpdklab
2024-06-04 23:22 ` dpdklab
2024-06-04 23:22 ` dpdklab
2024-06-04 23:23 ` dpdklab
2024-06-04 23:23 ` dpdklab
2024-06-04 23:24 ` dpdklab
2024-06-04 23:24 ` dpdklab
2024-06-04 23:24 ` dpdklab
2024-06-04 23:25 ` dpdklab
2024-06-04 23:25 ` dpdklab
2024-06-04 23:26 ` dpdklab
2024-06-04 23:27 ` dpdklab
2024-06-04 23:27 ` dpdklab
2024-06-04 23:27 ` dpdklab
2024-06-04 23:28 ` dpdklab
2024-06-04 23:28 ` dpdklab
2024-06-04 23:28 ` dpdklab
2024-06-04 23:29 ` dpdklab
2024-06-04 23:29 ` dpdklab
2024-06-04 23:29 ` dpdklab
2024-06-04 23:30 ` dpdklab
2024-06-04 23:30 ` dpdklab
2024-06-04 23:30 ` dpdklab
2024-06-04 23:31 ` dpdklab
2024-06-04 23:31 ` dpdklab
2024-06-04 23:32 ` dpdklab
2024-06-04 23:32 ` dpdklab
2024-06-04 23:32 ` dpdklab
2024-06-04 23:34 ` dpdklab
2024-06-04 23:34 ` dpdklab
2024-06-04 23:35 ` dpdklab
2024-06-04 23:36 ` dpdklab
2024-06-04 23:36 ` dpdklab
2024-06-04 23:37 ` dpdklab
2024-06-04 23:37 ` dpdklab
2024-06-04 23:37 ` dpdklab
2024-06-04 23:38 ` dpdklab
2024-06-04 23:39 ` dpdklab
2024-06-04 23:40 ` dpdklab
2024-06-04 23:40 ` dpdklab
2024-06-04 23:42 ` dpdklab
2024-06-04 23:44 ` dpdklab
2024-06-04 23:45 ` dpdklab
2024-06-04 23:48 ` dpdklab
2024-06-04 23:50 ` dpdklab
2024-06-04 23:50 ` dpdklab
2024-06-04 23:52 ` dpdklab
2024-06-04 23:55 ` |WARNING| " dpdklab
2024-06-04 23:56 ` dpdklab
2024-06-04 23:56 ` dpdklab
2024-06-05  0:01 ` dpdklab
2024-06-05  0:04 ` dpdklab
2024-06-05  0:05 ` dpdklab
2024-06-05  0:06 ` dpdklab
2024-06-05  0:08 ` dpdklab
2024-06-05  0:10 ` dpdklab
2024-06-05  0:18 ` |SUCCESS| " dpdklab
2024-06-05  0:20 ` dpdklab
2024-06-05  0:28 ` |WARNING| " dpdklab
2024-06-05  0:44 ` |SUCCESS| " dpdklab
2024-06-05  0:58 ` |WARNING| " dpdklab
2024-06-05  1:06 ` |SUCCESS| " dpdklab
2024-06-05  1:49 ` dpdklab
2024-06-05 21:17 ` 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=665f9ae2.630a0220.b9a62.9f73SMTPIN_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).