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] cadb255e25d690d719d6f159e0a63f8be60650a5
Date: Tue, 18 Jan 2022 15:24:20 +0000 (UTC)	[thread overview]
Message-ID: <20220118152420.0EA9A602B7@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 4052 bytes --]

_Testing PASS_

Branch: dpdk

cadb255e25d690d719d6f159e0a63f8be60650a5 --> testing pass

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | PASS               | PASS                 |
+---------------------+--------------------+----------------------+
| RHEL8               | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| FreeBSD 13          | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| RHEL 7              | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Arch Linux          | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 31           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 33           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 32           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Alpine              | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 18.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15    | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS 8            | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 34           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 34 clang     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+


Windows Server 2019
	Kernel: 10.0
	Compiler: clang 9.0 and gcc 8.1.0 (MinGW)

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

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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)

Arch Linux
	Kernel: 5.4.0-73-generic
	Compiler: gcc 11.1.0

Fedora 31
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.1

Fedora 33
	Kernel: 5.4.0-72-generic
	Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

Fedora 32
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 10.2.1

Alpine
	Kernel: 5.4.0-73-generic
	Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424

Ubuntu 18.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0-3ubuntu1~18.04

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

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

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

Fedora 34
	Kernel: 5.4.0-72-generic
	Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)

Fedora 34 clang
	Kernel: 5.4.0-72-generic
	Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-01-18 15:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 15:24 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-01-18 23:30 dpdklab
2022-01-18 23:13 dpdklab
2022-01-18 22:12 dpdklab
2022-01-18 21:59 dpdklab
2022-01-18 16:00 dpdklab
2022-01-18 15:50 dpdklab
2022-01-18 15:38 dpdklab
2022-01-18 15:35 dpdklab
2022-01-18 15:31 dpdklab
2022-01-18 15:30 dpdklab
2022-01-18 15:25 dpdklab
2022-01-18 15:20 dpdklab
2022-01-18 15:15 dpdklab
2022-01-18 15:13 dpdklab
2022-01-17 23:49 dpdklab
2022-01-17 23:41 dpdklab
2022-01-17 23:33 dpdklab
2022-01-17 23:21 dpdklab
2022-01-17 23:12 dpdklab
2022-01-17 23:09 dpdklab
2022-01-17 23:08 dpdklab
2022-01-17 23:07 dpdklab
2022-01-17 23:02 dpdklab
2022-01-17 22:59 dpdklab
2022-01-17 22:57 dpdklab
2022-01-17 22:54 dpdklab
2022-01-17 22:54 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=20220118152420.0EA9A602B7@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --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).