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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw108253 [PATCH] common/cnxk: support B0 variant
Date: Thu, 24 Feb 2022 16:10:33 +0000 (UTC)	[thread overview]
Message-ID: <20220224161033.DAA75601F2@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-x86_64-compile-testing
Test-Status: SUCCESS
http://dpdk.org/patch/108253

_Testing PASS_

Submitter: Tomasz Duszynski <tduszynski@marvell.com>
Date: Thursday, February 24 2022 10:42:36 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ee05a93e1e6633d0fdec409faf09f12a2e05b991

108253 --> testing pass

Test environment and result as below:

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


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

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

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)

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

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

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

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

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

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)

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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-02-24 16:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 16:10 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-25  8:14 dpdklab
2022-02-24 16:42 dpdklab
2022-02-24 15:16 dpdklab
2022-02-24 15:16 dpdklab
2022-02-24 13:43 dpdklab
2022-02-24 13:34 dpdklab
2022-02-24 13:34 dpdklab
2022-02-24 13:32 dpdklab
2022-02-24 13:24 dpdklab
2022-02-24 13:24 dpdklab
2022-02-24 13:22 dpdklab
2022-02-24 13:21 dpdklab
2022-02-24 13:18 dpdklab
     [not found] <20220224104236.1425812-1-tduszynski@marvell.com>
2022-02-24 10:44 ` checkpatch
2022-02-24 12:38 ` 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=20220224161033.DAA75601F2@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).