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| pw129651 [PATCH] [v11,1/1] dts: add smoke tests
Date: Wed, 19 Jul 2023 14:24:08 -0700 (PDT)	[thread overview]
Message-ID: <64b85478.920a0220.4f99a.962eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Wednesday, July 19 2023 20:16:54 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:238f67ca9cc00be4248b14d9ca4412edb7da62f6

129651 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| Fedora 37        | PASS     |
+------------------+----------+
| RHEL8            | PASS     |
+------------------+----------+
| Debian Bullseye  | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| RHEL 7           | PASS     |
+------------------+----------+
| Fedora 38        | PASS     |
+------------------+----------+
| Debian Buster    | PASS     |
+------------------+----------+
| CentOS Stream 8  | PASS     |
+------------------+----------+


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

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

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

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

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)

Fedora 38
	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 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-07-19 21:24 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19 21:24 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-19 23:55 dpdklab
2023-07-19 22:30 dpdklab
2023-07-19 22:25 dpdklab
2023-07-19 22:20 dpdklab
2023-07-19 22:09 dpdklab
2023-07-19 22:04 dpdklab
2023-07-19 21:54 dpdklab
2023-07-19 21:30 dpdklab
2023-07-19 21:29 dpdklab
2023-07-19 21:26 dpdklab
2023-07-19 21:25 dpdklab
2023-07-19 21:24 dpdklab
2023-07-19 21:22 dpdklab
2023-07-19 21:21 dpdklab
     [not found] <20230719201807.12708-3-jspewock@iol.unh.edu>
2023-07-19 20:06 ` |SUCCESS| pw129651 [PATCH v11 1/1] " qemudev
2023-07-19 20:10 ` qemudev
2023-07-19 20:19 ` checkpatch
2023-07-19 21:18 ` 0-day Robot
2023-07-19 21:16 |SUCCESS| pw129651 [PATCH] [v11,1/1] " dpdklab
2023-07-19 21:16 dpdklab
2023-07-19 21:16 dpdklab
2023-07-19 21:05 dpdklab
2023-07-19 21:04 dpdklab
2023-07-19 21:03 dpdklab
2023-07-19 21:03 dpdklab
2023-07-19 21:02 dpdklab
2023-07-19 21:02 dpdklab
2023-07-19 21:02 dpdklab
2023-07-19 21:02 dpdklab
2023-07-19 21:02 dpdklab
2023-07-19 21:01 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=64b85478.920a0220.4f99a.962eSMTPIN_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).