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| pw141524-141529 [PATCH] [6/6] common/cnxk: flow aginig del
Date: Mon, 24 Jun 2024 03:54:40 -0700 (PDT)	[thread overview]
Message-ID: <66795070.050a0220.a011d.9efcSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240624074822.88955-6-hkalra@marvell.com>

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

_Testing PASS_

Submitter: Harman Kalra <hkalra@marvell.com>
Date: Monday, June 24 2024 07:48:21 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:4a44d97f0a52a76258c6a6cb6a713f4380a8ab1f

141524-141529 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| Fedora 40        | PASS     |
+------------------+----------+
| Fedora 38        | PASS     |
+------------------+----------+
| Fedora 39        | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| Debian Bullseye  | PASS     |
+------------------+----------+
| Debian 12        | PASS     |
+------------------+----------+
| Fedora 37        | PASS     |
+------------------+----------+
| CentOS Stream 8  | PASS     |
+------------------+----------+
| CentOS Stream 9  | PASS     |
+------------------+----------+


Fedora 40
	Kernel: Depends on container host
	Compiler: clang 18.1.6

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.6

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

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

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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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

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

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

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-24 10:54 UTC|newest]

Thread overview: 113+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240624074822.88955-6-hkalra@marvell.com>
2024-06-24  7:23 ` |SUCCESS| pw141524-141529 [PATCH 6/6] common/cnxk: flow aginig delaying app shutdown qemudev
2024-06-24  7:27 ` qemudev
2024-06-24  7:51 ` |SUCCESS| pw141529 " checkpatch
2024-06-24  8:44 ` |FAILURE| " 0-day Robot
2024-06-24 10:03 ` |SUCCESS| pw141524-141529 [PATCH] [6/6] common/cnxk: flow aginig del dpdklab
2024-06-24 10:07 ` dpdklab
2024-06-24 10:14 ` dpdklab
2024-06-24 10:15 ` dpdklab
2024-06-24 10:16 ` dpdklab
2024-06-24 10:16 ` dpdklab
2024-06-24 10:19 ` dpdklab
2024-06-24 10:19 ` dpdklab
2024-06-24 10:19 ` dpdklab
2024-06-24 10:19 ` dpdklab
2024-06-24 10:30 ` dpdklab
2024-06-24 10:36 ` dpdklab
2024-06-24 10:38 ` dpdklab
2024-06-24 10:39 ` dpdklab
2024-06-24 10:40 ` dpdklab
2024-06-24 10:46 ` dpdklab
2024-06-24 10:54 ` dpdklab [this message]
2024-06-24 10:55 ` dpdklab
2024-06-24 10:57 ` dpdklab
2024-06-24 10:58 ` dpdklab
2024-06-24 11:07 ` dpdklab
2024-06-24 11:29 ` dpdklab
2024-06-24 11:29 ` dpdklab
2024-06-24 11:30 ` dpdklab
2024-06-24 11:30 ` dpdklab
2024-06-24 11:32 ` dpdklab
2024-06-24 11:34 ` dpdklab
2024-06-24 11:35 ` dpdklab
2024-06-24 11:36 ` dpdklab
2024-06-24 11:36 ` dpdklab
2024-06-24 11:36 ` dpdklab
2024-06-24 11:37 ` dpdklab
2024-06-24 11:37 ` dpdklab
2024-06-24 11:38 ` dpdklab
2024-06-24 11:38 ` dpdklab
2024-06-24 11:38 ` dpdklab
2024-06-24 11:39 ` dpdklab
2024-06-24 11:39 ` |FAILURE| " dpdklab
2024-06-24 11:39 ` dpdklab
2024-06-24 11:41 ` dpdklab
2024-06-24 11:41 ` dpdklab
2024-06-24 11:42 ` dpdklab
2024-06-24 11:43 ` dpdklab
2024-06-24 11:58 ` dpdklab
2024-06-24 11:58 ` dpdklab
2024-06-24 12:25 ` dpdklab
2024-06-24 12:25 ` dpdklab
2024-06-24 12:26 ` dpdklab
2024-06-24 12:26 ` dpdklab
2024-06-24 12:27 ` dpdklab
2024-06-24 12:28 ` dpdklab
2024-06-24 12:30 ` dpdklab
2024-06-24 12:30 ` dpdklab
2024-06-24 12:31 ` dpdklab
2024-06-24 12:34 ` dpdklab
2024-06-24 12:49 ` dpdklab
2024-06-24 12:49 ` dpdklab
2024-06-24 12:50 ` dpdklab
2024-06-24 12:51 ` dpdklab
2024-06-24 13:05 ` dpdklab
2024-06-24 13:06 ` dpdklab
2024-06-24 13:07 ` dpdklab
2024-06-24 13:07 ` dpdklab
2024-06-24 13:07 ` dpdklab
2024-06-24 13:08 ` dpdklab
2024-06-24 13:09 ` dpdklab
2024-06-24 13:11 ` dpdklab
2024-06-24 13:11 ` dpdklab
2024-06-24 13:13 ` dpdklab
2024-06-24 13:13 ` dpdklab
2024-06-24 13:14 ` dpdklab
2024-06-24 13:14 ` dpdklab
2024-06-24 13:15 ` dpdklab
2024-06-24 13:17 ` dpdklab
2024-06-24 13:18 ` dpdklab
2024-06-24 13:19 ` dpdklab
2024-06-24 13:20 ` dpdklab
2024-06-24 13:20 ` dpdklab
2024-06-24 13:21 ` dpdklab
2024-06-24 13:21 ` dpdklab
2024-06-24 13:22 ` dpdklab
2024-06-24 13:25 ` dpdklab
2024-06-24 13:26 ` dpdklab
2024-06-24 13:27 ` dpdklab
2024-06-24 13:35 ` dpdklab
2024-06-24 13:35 ` dpdklab
2024-06-24 13:35 ` dpdklab
2024-06-24 13:36 ` dpdklab
2024-06-24 13:36 ` dpdklab
2024-06-24 13:36 ` dpdklab
2024-06-24 13:36 ` dpdklab
2024-06-24 13:37 ` dpdklab
2024-06-24 13:37 ` dpdklab
2024-06-24 13:38 ` dpdklab
2024-06-24 13:38 ` dpdklab
2024-06-24 13:46 ` dpdklab
2024-06-24 13:47 ` dpdklab
2024-06-24 13:47 ` dpdklab
2024-06-24 13:48 ` dpdklab
2024-06-24 13:49 ` dpdklab
2024-06-24 13:49 ` dpdklab
2024-06-24 13:51 ` dpdklab
2024-06-24 14:06 ` dpdklab
2024-06-24 14:13 ` dpdklab
2024-06-24 14:14 ` dpdklab
2024-06-24 14:22 ` dpdklab
2024-06-24 14:25 ` dpdklab
2024-06-24 14:27 ` dpdklab
2024-06-24 15:57 ` |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=66795070.050a0220.a011d.9efcSMTPIN_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).