automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Juraj Linkes <juraj.linkes@pantheon.tech>,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw126333 [PATCH] [v1] dts: create tarball from git ref
Date: Thu, 20 Apr 2023 21:16:01 -0700 (PDT)	[thread overview]
Message-ID: <64420e01.170a0220.96e2c.269aSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Juraj Linkes <juraj.linkes@pantheon.tech>
Date: Thursday, April 20 2023 14:02:44 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5f34cc454df420b9b2da8deb949fb76cba058b87

126333 --> testing pass

Test environment and result as below:

+------------------+----------+
|   Environment    | abi_test |
+==================+==========+
| CentOS Stream 9  | PASS     |
+------------------+----------+
| Ubuntu 22.04     | PASS     |
+------------------+----------+
| RHEL 7           | PASS     |
+------------------+----------+
| RHEL8            | PASS     |
+------------------+----------+
| openSUSE Leap 15 | PASS     |
+------------------+----------+
| Debian Bullseye  | PASS     |
+------------------+----------+


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

Ubuntu 22.04
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.1-2

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)

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-04-21  4:16 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21  4:16 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-21 19:24 dpdklab
2023-04-21  6:02 dpdklab
2023-04-21  5:50 dpdklab
2023-04-21  5:49 dpdklab
2023-04-21  5:32 dpdklab
2023-04-21  4:42 dpdklab
2023-04-21  4:39 dpdklab
2023-04-21  4:29 dpdklab
2023-04-21  4:27 dpdklab
2023-04-21  4:20 dpdklab
2023-04-21  4:17 dpdklab
2023-04-21  4:13 dpdklab
2023-04-21  4:01 dpdklab
2023-04-21  3:57 dpdklab
2023-04-21  3:53 dpdklab
2023-04-21  3:35 dpdklab
2023-04-21  3:26 dpdklab
2023-04-21  3:24 dpdklab
2023-04-21  3:21 dpdklab
2023-04-21  3:18 dpdklab
2023-04-21  3:10 dpdklab
2023-04-21  3:09 dpdklab
2023-04-21  3:06 dpdklab
2023-04-21  3:01 dpdklab
     [not found] <20230420140244.701467-1-juraj.linkes@pantheon.tech>
2023-04-20 14:04 ` |SUCCESS| pw126333 [PATCH v1] " qemudev
2023-04-20 14:08 ` qemudev
2023-04-20 14:16 ` checkpatch
2023-04-20 15:19 ` 0-day Robot

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=64420e01.170a0220.96e2c.269aSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=juraj.linkes@pantheon.tech \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).