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| pw129437 [PATCH] [v3] bus/cdx: provide driver flag for opt
Date: Tue, 11 Jul 2023 18:39:18 -0700 (PDT)	[thread overview]
Message-ID: <64ae0446.050a0220.1436.8e64SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/129437

_Testing PASS_

Submitter: Abhijit Gangurde <abhijit.gangurde@amd.com>
Date: Tuesday, July 11 2023 05:51:47 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:623dc9364dc6a818799941cc26dc8f70feb2bb24

129437 --> testing pass

Test environment and result as below:

+--------------------------+----------------+
|       Environment        | dpdk_unit_test |
+==========================+================+
| Debian 11 (Buster) (ARM) | PASS           |
+--------------------------+----------------+
| CentOS Stream 9 (ARM)    | PASS           |
+--------------------------+----------------+
| Fedora 38 (ARM)          | PASS           |
+--------------------------+----------------+
| Fedora 37 (ARM)          | PASS           |
+--------------------------+----------------+
| Ubuntu 20.04 (ARM)       | PASS           |
+--------------------------+----------------+
| Fedora 38 (ARM Clang)    | PASS           |
+--------------------------+----------------+
| Debian Buster            | PASS           |
+--------------------------+----------------+
| CentOS Stream 9          | PASS           |
+--------------------------+----------------+
| Debian Bullseye          | PASS           |
+--------------------------+----------------+
| RHEL 7                   | PASS           |
+--------------------------+----------------+
| Ubuntu 20.04             | PASS           |
+--------------------------+----------------+
| Ubuntu 22.04             | PASS           |
+--------------------------+----------------+
| Fedora 38                | PASS           |
+--------------------------+----------------+
| openSUSE Leap 15         | PASS           |
+--------------------------+----------------+
| CentOS Stream 8          | PASS           |
+--------------------------+----------------+
| RHEL8                    | PASS           |
+--------------------------+----------------+
| Fedora 37                | PASS           |
+--------------------------+----------------+


Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.3

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

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

RHEL 7
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

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/27036/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-07-12  1:39 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12  1:39 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-14 15:24 dpdklab
2023-07-14 15:18 dpdklab
2023-07-14 15:13 dpdklab
2023-07-13 18:37 dpdklab
2023-07-13 18:36 dpdklab
2023-07-13 16:18 dpdklab
2023-07-13 16:16 dpdklab
2023-07-12 12:16 dpdklab
2023-07-12 12:12 dpdklab
2023-07-12 11:56 dpdklab
2023-07-12 11:51 dpdklab
2023-07-12 11:23 dpdklab
2023-07-12 11:16 dpdklab
2023-07-12  5:52 dpdklab
2023-07-12  5:51 dpdklab
2023-07-12  4:49 dpdklab
2023-07-11 22:38 dpdklab
2023-07-11 22:37 dpdklab
2023-07-11 22:08 dpdklab
2023-07-11 22:05 dpdklab
2023-07-11 22:05 dpdklab
2023-07-11 21:57 dpdklab
2023-07-11 21:56 dpdklab
2023-07-11 21:49 dpdklab
2023-07-11 21:47 dpdklab
2023-07-11 21:42 dpdklab
2023-07-11 21:40 dpdklab
2023-07-11 21:34 dpdklab
2023-07-11 21:33 dpdklab
2023-07-11 18:42 dpdklab
2023-07-11 18:27 dpdklab
2023-07-11 18:26 dpdklab
2023-07-11 18:26 dpdklab
2023-07-11 18:24 dpdklab
2023-07-11 18:24 dpdklab
2023-07-11 18:23 dpdklab
2023-07-11 18:22 dpdklab
2023-07-11 18:20 dpdklab
2023-07-11 17:49 dpdklab
2023-07-11 17:44 dpdklab
2023-07-11 16:05 dpdklab
2023-07-11 15:49 dpdklab
2023-07-11 15:47 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=64ae0446.050a0220.1436.8e64SMTPIN_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).