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] |WARNING| pw95634-95637 [PATCH] [V4, 5/5] examples/pipeline: add selector example
Date: Sat, 10 Jul 2021 00:23:50 -0400 (EDT)	[thread overview]
Message-ID: <20210710042350.3DE79B0F7@noxus.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/95637

_Testing issues_

Submitter: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
Date: Saturday, July 10 2021 00:20:36 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:cac2a49b4ae5e24078b43b2f8b7cd083f74620b9

95634-95637 --> testing fail

Test environment and result as below:

+------------------------------------+----------+
|            Environment             | abi_test |
+====================================+==========+
| FreeBSD 13                         | FAIL     |
+------------------------------------+----------+
| Ubuntu 18.04 ARM                   | PASS     |
+------------------------------------+----------+
| Ubuntu 18.04                       | PASS     |
+------------------------------------+----------+
| RHEL 7                             | PASS     |
+------------------------------------+----------+
| RHEL8                              | PASS     |
+------------------------------------+----------+
| Arch Linux                         | PASS     |
+------------------------------------+----------+
| Ubuntu 20.04                       | PASS     |
+------------------------------------+----------+
| CentOS 8                           | PASS     |
+------------------------------------+----------+
| Fedora 32                          | PASS     |
+------------------------------------+----------+
| CentOS Stream 8                    | PASS     |
+------------------------------------+----------+
| openSUSE Leap 15                   | PASS     |
+------------------------------------+----------+
| Fedora 31                          | PASS     |
+------------------------------------+----------+
| Ubuntu 20.04 ARM cross-compilation | PASS     |
+------------------------------------+----------+
| Fedora 34 clang                    | PASS     |
+------------------------------------+----------+
| Fedora 33                          | PASS     |
+------------------------------------+----------+
| Fedora 34                          | PASS     |
+------------------------------------+----------+

==== 20 line log output for FreeBSD 13 (abi_test): ====

Functions changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

Functions changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added (1 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

Functions changes summary: 0 Removed, 0 Changed (10 filtered out), 0 Added (1 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

Functions changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

Error: cannot find librte_event_octeontx.dump in build_install
Functions changes summary: 0 Removed, 0 Changed, 0 Added (6 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

Functions changes summary: 0 Removed, 0 Changed (54 filtered out), 0 Added (11 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

==== End log output ====

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

Ubuntu 18.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0-3ubuntu1~18.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)

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

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.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)

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

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

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

Ubuntu 20.04 ARM cross-compilation
	Kernel: 5.4.0-72-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

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

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)

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

UNH-IOL DPDK Community Lab

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

                 reply	other threads:[~2021-07-10  4:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210710042350.3DE79B0F7@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).