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| pw129455-129468 [PATCH] [v9,14/14] eal: do not define type
Date: Tue, 11 Jul 2023 19:08:03 -0700 (PDT)	[thread overview]
Message-ID: <64ae0b03.250a0220.d9b2.be1fSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Testing PASS_

Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tuesday, July 11 2023 16:49:17 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:623dc9364dc6a818799941cc26dc8f70feb2bb24

129455-129468 --> testing pass

Test environment and result as below:

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


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

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

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

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)

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

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  2:08 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12  2:08 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-07-12 16:10 dpdklab
2023-07-12 15:44 dpdklab
2023-07-12 15:25 dpdklab
2023-07-12 15:20 dpdklab
2023-07-12 14:46 dpdklab
2023-07-12 14:43 dpdklab
2023-07-12 14:24 dpdklab
2023-07-12 14:19 dpdklab
2023-07-12 14:15 dpdklab
2023-07-12 14:04 dpdklab
2023-07-12 13:33 dpdklab
2023-07-12 13:04 dpdklab
2023-07-12  8:41 dpdklab
2023-07-12  8:11 dpdklab
2023-07-12  6:51 dpdklab
2023-07-12  6:51 dpdklab
2023-07-12  6:20 dpdklab
2023-07-12  6:19 dpdklab
2023-07-12  3:29 dpdklab
2023-07-12  2:14 dpdklab
2023-07-12  2:11 dpdklab
2023-07-12  2:09 dpdklab
2023-07-12  2:07 dpdklab
2023-07-12  2:06 dpdklab
2023-07-12  2:04 dpdklab
2023-07-12  1:52 dpdklab
2023-07-12  1:51 dpdklab
2023-07-12  1:50 dpdklab
2023-07-12  1:50 dpdklab
2023-07-12  1:49 dpdklab
2023-07-12  1:49 dpdklab
2023-07-12  1:48 dpdklab
2023-07-12  1:46 dpdklab
2023-07-12  1:45 dpdklab
2023-07-12  1:40 dpdklab
2023-07-12  1:39 dpdklab
2023-07-12  1:39 dpdklab
2023-07-12  1:32 dpdklab
2023-07-12  1:30 dpdklab
2023-07-12  1:27 dpdklab
2023-07-12  1:26 dpdklab
2023-07-12  1:26 dpdklab
2023-07-12  1:24 dpdklab
2023-07-12  1:23 dpdklab
2023-07-12  1:22 dpdklab
2023-07-12  1:21 dpdklab
2023-07-12  1:20 dpdklab
2023-07-12  1:20 dpdklab
2023-07-12  1:19 dpdklab
2023-07-12  1:18 dpdklab
2023-07-12  1:17 dpdklab
2023-07-12  1:16 dpdklab
2023-07-12  1:10 dpdklab
2023-07-12  1:09 dpdklab
2023-07-12  1:08 dpdklab
2023-07-12  1:06 dpdklab
2023-07-12  1:06 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=64ae0b03.250a0220.d9b2.be1fSMTPIN_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).