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: [dpdk-test-report] |SUCCESS| pw92252 [PATCH] [v4] net/bonding: fix socket id check
Date: Tue, 27 Apr 2021 09:16:11 -0400 (EDT)	[thread overview]
Message-ID: <20210427131611.5FC1630576@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_Testing PASS_

Submitter: Min Hu (Connor) <humin29@huawei.com>
Date: Tuesday, April 27 2021 11:39:41 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:1b593b9c832e9b284cc59665fe662242a3fc1daf

92252 --> testing pass

Test environment and result as below:

+---------------------+----------------------+-------------------+--------------------+----------------+
|     Environment     | dpdk_mingw64_compile | dpdk_compile_spdk | dpdk_meson_compile | dpdk_unit_test |
+=====================+======================+===================+====================+================+
| Windows Server 2019 | PASS                 | SKIPPED           | PASS               | SKIPPED        |
+---------------------+----------------------+-------------------+--------------------+----------------+
| Ubuntu 18.04        | SKIPPED              | PASS              | PASS               | PASS           |
+---------------------+----------------------+-------------------+--------------------+----------------+
| Fedora 31           | SKIPPED              | SKIPPED           | PASS               | SKIPPED        |
+---------------------+----------------------+-------------------+--------------------+----------------+
| CentOS Stream 8     | SKIPPED              | SKIPPED           | PASS               | SKIPPED        |
+---------------------+----------------------+-------------------+--------------------+----------------+
| Fedora 32           | SKIPPED              | SKIPPED           | PASS               | SKIPPED        |
+---------------------+----------------------+-------------------+--------------------+----------------+
| RHEL8               | SKIPPED              | SKIPPED           | PASS               | SKIPPED        |
+---------------------+----------------------+-------------------+--------------------+----------------+
| Arch Linux          | SKIPPED              | SKIPPED           | PASS               | SKIPPED        |
+---------------------+----------------------+-------------------+--------------------+----------------+
| openSUSE Leap 15    | SKIPPED              | SKIPPED           | PASS               | SKIPPED        |
+---------------------+----------------------+-------------------+--------------------+----------------+
| RHEL 7              | SKIPPED              | SKIPPED           | PASS               | SKIPPED        |
+---------------------+----------------------+-------------------+--------------------+----------------+
| Ubuntu 20.04        | SKIPPED              | SKIPPED           | PASS               | SKIPPED        |
+---------------------+----------------------+-------------------+--------------------+----------------+
| FreeBSD 11.2        | SKIPPED              | SKIPPED           | PASS               | SKIPPED        |
+---------------------+----------------------+-------------------+--------------------+----------------+
| Ubuntu 18.04 ARM    | SKIPPED              | SKIPPED           | PASS               | PASS           |
+---------------------+----------------------+-------------------+--------------------+----------------+


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

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

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

Arch Linux
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 10.2.0

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

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)

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

FreeBSD 11.2
	Kernel: 11.2
	Compiler: gcc 8.3

Ubuntu 18.04 ARM
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-04-27 13:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-27 13:16 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-04-29  0:17 dpdklab
2021-04-27 13:15 dpdklab
2021-04-27 12:40 dpdklab
2021-04-27 12:33 dpdklab
2021-04-27 12:26 dpdklab
2021-04-27 12:26 dpdklab
     [not found] <1619523581-60870-1-git-send-email-humin29@huawei.com>
2021-04-27 11:39 ` [dpdk-test-report] |SUCCESS| pw92252 [PATCH v4] " 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=20210427131611.5FC1630576@noxus.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).