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| pw140911 [PATCH] [v1] dts: Testbed And Node Configuration
Date: Wed, 12 Jun 2024 15:57:31 -0700 (PDT)	[thread overview]
Message-ID: <666a27db.050a0220.f4af9.0391SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240610193410.17968-2-npratte@iol.unh.edu>

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

_Testing PASS_

Submitter: Nicholas Pratte <npratte@iol.unh.edu>
Date: Monday, June 10 2024 19:34:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:76cef1af8bdaeaf67a5c4ca5df3f221df994dc46

140911 --> testing pass

Test environment and result as below:

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


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

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

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

Ubuntu 22.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.0

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

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

Debian 12
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.0

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

RHEL8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)

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

Ubuntu 24.04
	Kernel: 5.4.0-167-generic
	Compiler: gcc 13.2.0

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

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-12 22:57 UTC|newest]

Thread overview: 107+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240610193410.17968-2-npratte@iol.unh.edu>
2024-06-10 19:07 ` |SUCCESS| pw140911 [PATCH v1] dts: Testbed And Node Configuration Split qemudev
2024-06-10 19:11 ` qemudev
2024-06-10 19:35 ` checkpatch
2024-06-10 20:24 ` |FAILURE| " 0-day Robot
2024-06-10 23:38 ` |SUCCESS| pw140911 [PATCH] [v1] dts: Testbed And Node Configuration dpdklab
2024-06-10 23:39 ` dpdklab
2024-06-10 23:54 ` dpdklab
2024-06-11  0:02 ` dpdklab
2024-06-11  0:16 ` dpdklab
2024-06-11  1:16 ` dpdklab
2024-06-12 22:56 ` dpdklab
2024-06-12 22:57 ` dpdklab [this message]
2024-06-12 22:58 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 22:59 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:00 ` dpdklab
2024-06-12 23:01 ` dpdklab
2024-06-12 23:01 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:02 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:03 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:04 ` dpdklab
2024-06-12 23:05 ` dpdklab
2024-06-12 23:07 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:08 ` dpdklab
2024-06-12 23:09 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:10 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:11 ` dpdklab
2024-06-12 23:12 ` dpdklab
2024-06-12 23:12 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:13 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:14 ` dpdklab
2024-06-12 23:15 ` dpdklab
2024-06-12 23:15 ` dpdklab
2024-06-12 23:15 ` dpdklab
2024-06-12 23:15 ` dpdklab
2024-06-12 23:15 ` dpdklab
2024-06-12 23:15 ` dpdklab
2024-06-12 23:16 ` dpdklab
2024-06-12 23:16 ` dpdklab
2024-06-12 23:16 ` dpdklab
2024-06-12 23:17 ` dpdklab
2024-06-12 23:17 ` dpdklab
2024-06-12 23:17 ` dpdklab
2024-06-12 23:18 ` dpdklab
2024-06-12 23:19 ` dpdklab
2024-06-12 23:19 ` dpdklab
2024-06-12 23:19 ` dpdklab
2024-06-12 23:20 ` dpdklab
2024-06-12 23:21 ` dpdklab
2024-06-12 23:22 ` dpdklab
2024-06-12 23:24 ` dpdklab
2024-06-12 23:26 ` dpdklab
2024-06-12 23:26 ` dpdklab
2024-06-12 23:27 ` dpdklab
2024-06-12 23:28 ` dpdklab
2024-06-12 23:29 ` dpdklab
2024-06-12 23:29 ` dpdklab
2024-06-12 23:30 ` dpdklab
2024-06-12 23:31 ` dpdklab
2024-06-12 23:32 ` dpdklab
2024-06-12 23:32 ` dpdklab
2024-06-12 23:32 ` dpdklab
2024-06-12 23:32 ` dpdklab
2024-06-12 23:32 ` dpdklab
2024-06-12 23:32 ` dpdklab
2024-06-12 23:33 ` dpdklab
2024-06-12 23:33 ` dpdklab
2024-06-12 23:33 ` dpdklab
2024-06-12 23:33 ` dpdklab
2024-06-12 23:33 ` dpdklab
2024-06-12 23:34 ` dpdklab
2024-06-12 23:34 ` dpdklab
2024-06-12 23:35 ` dpdklab
2024-06-12 23:37 ` 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=666a27db.050a0220.f4af9.0391SMTPIN_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).