automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: [dpdk-test-report] |SUCCESS| pw102125 [PATCH] [v1] maintainers: update for driver testing tool
Date: Tue, 19 Oct 2021 01:22:46 -0400 (EDT)	[thread overview]
Message-ID: <20211019052246.3DC4A60524@noxus.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-x86_64-unit-testing
Test-Status: SUCCESS
http://dpdk.org/patch/102125

_Testing PASS_

Submitter: Yuying Zhang <yuying.zhang@intel.com>
Date: Tuesday, October 19 2021 06:17:11 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:821f60c7f4337d74a0c8e4add4095be524d77600

102125 --> testing pass

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| Arch Linux       | PASS           |
+------------------+----------------+
| Ubuntu 18.04     | PASS           |
+------------------+----------------+
| Fedora 31        | PASS           |
+------------------+----------------+
| RHEL 7           | PASS           |
+------------------+----------------+
| CentOS Stream 8  | PASS           |
+------------------+----------------+
| Fedora 32        | PASS           |
+------------------+----------------+
| RHEL8            | PASS           |
+------------------+----------------+
| CentOS 8         | PASS           |
+------------------+----------------+
| openSUSE Leap 15 | PASS           |
+------------------+----------------+
| Ubuntu 20.04     | PASS           |
+------------------+----------------+
| Fedora 33        | PASS           |
+------------------+----------------+
| Fedora 34        | PASS           |
+------------------+----------------+
| Fedora 34 clang  | PASS           |
+------------------+----------------+


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

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

Fedora 31
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.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)

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

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

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

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

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)

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/patchsets/19524/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-10-19  5:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19  5:22 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-10-19 12:10 dpdklab
2021-10-19 11:55 dpdklab
2021-10-19 11:40 dpdklab
2021-10-19  8:07 dpdklab
2021-10-19  7:55 dpdklab
2021-10-19  4:35 dpdklab
2021-10-19  4:22 dpdklab
2021-10-19  3:19 dpdklab
2021-10-19  3:18 dpdklab
2021-10-19  3:16 dpdklab
2021-10-19  3:04 dpdklab
2021-10-19  3:02 dpdklab
2021-10-19  3:02 dpdklab
     [not found] <20211019061711.585547-1-yuying.zhang@intel.com>
2021-10-19  2:35 ` [dpdk-test-report] |SUCCESS| pw102125 [PATCH v1] " checkpatch

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=20211019052246.3DC4A60524@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@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).