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| pw140161-140170 [PATCH] [10/10] net/cnxk: define CPT HW re
Date: Fri, 17 May 2024 13:01:42 -0700 (PDT)	[thread overview]
Message-ID: <6647b7a6.d40a0220.a6bb6.1938SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240517074448.3146611-10-ndabilpuram@marvell.com>

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

_Testing PASS_

Submitter: Nithin Dabilpuram <ndabilpuram@marvell.com>
Date: Friday, May 17 2024 07:44:48 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

140161-140170 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| CentOS Stream 8  | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| Debian 12        | PASS     |
+------------------+----------+


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

openSUSE Leap 15
	Kernel: 5.4.0-167-generic
	Compiler: gcc 7.5.0

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-05-17 20:01 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240517074448.3146611-10-ndabilpuram@marvell.com>
2024-05-17  7:20 ` |SUCCESS| pw140161-140170 [PATCH 10/10] net/cnxk: define CPT HW result format for PMD API qemudev
2024-05-17  7:25 ` qemudev
2024-05-17  7:46 ` |SUCCESS| pw140170 " checkpatch
2024-05-17  8:44 ` 0-day Robot
2024-05-17 19:35 ` |SUCCESS| pw140161-140170 [PATCH] [10/10] net/cnxk: define CPT HW re dpdklab
2024-05-17 19:36 ` dpdklab
2024-05-17 19:37 ` dpdklab
2024-05-17 19:38 ` dpdklab
2024-05-17 19:38 ` dpdklab
2024-05-17 19:40 ` dpdklab
2024-05-17 19:40 ` dpdklab
2024-05-17 19:41 ` dpdklab
2024-05-17 19:42 ` dpdklab
2024-05-17 19:44 ` dpdklab
2024-05-17 19:45 ` dpdklab
2024-05-17 19:45 ` dpdklab
2024-05-17 19:46 ` dpdklab
2024-05-17 19:47 ` dpdklab
2024-05-17 19:57 ` dpdklab
2024-05-17 20:00 ` dpdklab
2024-05-17 20:01 ` dpdklab [this message]
2024-05-17 20:02 ` dpdklab
2024-05-17 20:06 ` dpdklab
2024-05-17 20:11 ` dpdklab
2024-05-17 20:12 ` dpdklab
2024-05-17 20:19 ` dpdklab
2024-05-17 20:22 ` dpdklab
2024-05-17 20:23 ` dpdklab
2024-05-17 20:31 ` dpdklab
2024-05-17 20:39 ` dpdklab
2024-05-17 20:39 ` dpdklab
2024-05-17 20:45 ` dpdklab
2024-05-17 20:45 ` dpdklab
2024-05-17 20:45 ` dpdklab
2024-05-17 20:46 ` dpdklab
2024-05-17 20:46 ` dpdklab
2024-05-17 20:47 ` dpdklab
2024-05-17 20:49 ` dpdklab
2024-05-17 20:53 ` dpdklab
2024-05-17 20:57 ` dpdklab
2024-05-17 20:57 ` dpdklab
2024-05-17 20:58 ` dpdklab
2024-05-17 20:58 ` dpdklab
2024-05-17 21:02 ` dpdklab
2024-05-17 21:03 ` dpdklab
2024-05-17 21:03 ` dpdklab
2024-05-17 21:04 ` dpdklab
2024-05-17 21:06 ` dpdklab
2024-05-17 21:08 ` dpdklab
2024-05-17 21:08 ` dpdklab
2024-05-17 21:11 ` dpdklab
2024-05-17 21:12 ` dpdklab
2024-05-17 21:13 ` dpdklab
2024-05-17 21:14 ` dpdklab
2024-05-17 21:16 ` dpdklab
2024-05-17 21:17 ` dpdklab
2024-05-17 21:17 ` dpdklab
2024-05-17 21:17 ` dpdklab
2024-05-17 21:21 ` dpdklab
2024-05-17 21:21 ` dpdklab
2024-05-17 21:23 ` dpdklab
2024-05-17 21:24 ` dpdklab
2024-05-17 21:26 ` dpdklab
2024-05-17 21:28 ` dpdklab
2024-05-17 21:29 ` dpdklab
2024-05-17 21:30 ` dpdklab
2024-05-17 21:31 ` dpdklab
2024-05-17 21:33 ` dpdklab
2024-05-17 21:34 ` dpdklab
2024-05-17 21:36 ` dpdklab
2024-05-17 21:36 ` dpdklab
2024-05-17 21:36 ` dpdklab
2024-05-17 21:36 ` dpdklab
2024-05-17 21:37 ` dpdklab
2024-05-17 21:44 ` |FAILURE| " dpdklab
2024-05-17 21:45 ` |SUCCESS| " dpdklab
2024-05-17 21:45 ` dpdklab
2024-05-17 21:46 ` dpdklab
2024-05-17 21:49 ` dpdklab
2024-05-17 21:53 ` dpdklab
2024-05-17 21:53 ` dpdklab
2024-05-17 22:00 ` dpdklab
2024-05-17 22:02 ` dpdklab
2024-05-17 22:04 ` dpdklab
2024-05-17 22:12 ` dpdklab
2024-05-17 22:16 ` dpdklab
2024-05-17 22:16 ` dpdklab
2024-05-17 22:19 ` dpdklab
2024-05-17 22:56 ` dpdklab
2024-05-17 23:18 ` dpdklab
2024-05-17 23:35 ` dpdklab
2024-05-18  0:49 ` dpdklab
2024-05-23  6:16 ` 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=6647b7a6.d40a0220.a6bb6.1938SMTPIN_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).