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| pw136041-136044 [PATCH] [4/4] dts: log stderr with failed
Date: Mon, 22 Jan 2024 11:22:50 -0800 (PST)	[thread overview]
Message-ID: <65aec08a.170a0220.dd74b.57edSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Luca Vizzarro <luca.vizzarro@arm.com>
Date: Monday, January 22 2024 18:26:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:f1631b98727d2294008c8924f24a21366a8d383e

136041-136044 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| Debian Buster    | PASS     |
+------------------+----------+
| CentOS Stream 9  | PASS     |
+------------------+----------+
| Ubuntu 22.04     | PASS     |
+------------------+----------+
| Debian Bullseye  | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| Fedora 38        | PASS     |
+------------------+----------+


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

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-22 19:22 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 19:22 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-23  2:28 dpdklab
2024-01-23  2:21 dpdklab
2024-01-22 21:47 dpdklab
2024-01-22 20:41 dpdklab
2024-01-22 20:07 dpdklab
2024-01-22 19:55 dpdklab
2024-01-22 19:52 dpdklab
2024-01-22 19:50 dpdklab
2024-01-22 19:48 dpdklab
2024-01-22 19:46 dpdklab
2024-01-22 19:44 dpdklab
2024-01-22 19:42 dpdklab
2024-01-22 19:40 dpdklab
2024-01-22 19:39 dpdklab
2024-01-22 19:38 dpdklab
2024-01-22 19:36 dpdklab
2024-01-22 19:36 dpdklab
2024-01-22 19:32 dpdklab
2024-01-22 19:32 dpdklab
2024-01-22 19:31 dpdklab
2024-01-22 19:31 dpdklab
2024-01-22 19:30 dpdklab
2024-01-22 19:30 dpdklab
2024-01-22 19:29 dpdklab
2024-01-22 19:28 dpdklab
2024-01-22 19:28 dpdklab
2024-01-22 19:27 dpdklab
2024-01-22 19:27 dpdklab
2024-01-22 19:23 dpdklab
2024-01-22 19:23 dpdklab
2024-01-22 19:22 dpdklab
2024-01-22 19:21 dpdklab
2024-01-22 19:18 dpdklab
2024-01-22 19:18 dpdklab
2024-01-22 19:17 dpdklab
2024-01-22 19:15 dpdklab
2024-01-22 19:13 dpdklab
2024-01-22 19:13 dpdklab
2024-01-22 19:13 dpdklab
2024-01-22 19:13 dpdklab
2024-01-22 19:12 dpdklab
2024-01-22 19:11 dpdklab
2024-01-22 19:11 dpdklab
2024-01-22 19:10 dpdklab
2024-01-22 19:10 dpdklab
2024-01-22 19:09 dpdklab
2024-01-22 19:07 dpdklab
2024-01-22 19:07 dpdklab
2024-01-22 19:06 dpdklab
2024-01-22 19:06 dpdklab
2024-01-22 19:05 dpdklab
2024-01-22 19:05 dpdklab
2024-01-22 19:04 dpdklab
2024-01-22 19:04 dpdklab
2024-01-22 19:04 dpdklab
2024-01-22 19:04 dpdklab
2024-01-22 19:03 dpdklab
2024-01-22 19:03 dpdklab
2024-01-22 19:02 dpdklab
2024-01-22 19:02 dpdklab
2024-01-22 19:01 dpdklab
2024-01-22 19:01 dpdklab
2024-01-22 19:00 dpdklab
2024-01-22 18:59 dpdklab
2024-01-22 18:59 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=65aec08a.170a0220.dd74b.57edSMTPIN_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).