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| [GIT MASTER] b6c419dde10e9f5dec7a02098c48060a7493420c
Date: Mon, 12 Jun 2023 09:31:55 -0700 (PDT)	[thread overview]
Message-ID: <6487487b.050a0220.2c7b7.bb73SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing PASS_

Branch: dpdk

b6c419dde10e9f5dec7a02098c48060a7493420c --> testing pass

Test environment and result as below:

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


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

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

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

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)

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

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

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/24960/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-06-12 16:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 16:31 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-12 22:06 dpdklab
2023-06-12 19:35 dpdklab
2023-06-12 19:31 dpdklab
2023-06-12 19:21 dpdklab
2023-06-12 19:17 dpdklab
2023-06-12 19:01 dpdklab
2023-06-12 18:27 dpdklab
2023-06-12 17:50 dpdklab
2023-06-12 17:50 dpdklab
2023-06-12 17:30 dpdklab
2023-06-12 17:12 dpdklab
2023-06-12 17:12 dpdklab
2023-06-12 16:56 dpdklab
2023-06-12 16:53 dpdklab
2023-06-12 16:50 dpdklab
2023-06-12 16:43 dpdklab
2023-06-12 16:42 dpdklab
2023-06-12 16:36 dpdklab
2023-06-12 16:35 dpdklab
2023-06-12 16:20 dpdklab
2023-06-12 16:16 dpdklab
2023-06-12 16:16 dpdklab
2023-06-12 16:16 dpdklab
2023-06-12 16:15 dpdklab
2023-06-12 16:15 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=6487487b.050a0220.2c7b7.bb73SMTPIN_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).