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,
	"Morten Brørup" <mb@smartsharesystems.com>
Subject: |WARNING| pw105919 [PATCH] mempool: optimize put objects to mempool with cache
Date: Mon, 17 Jan 2022 15:26:03 +0000 (UTC)	[thread overview]
Message-ID: <20220117152603.11378602B7@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

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

_Testing issues_

Submitter: Morten Brørup <mb@smartsharesystems.com>
Date: Monday, January 17 2022 11:52:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:6f716880ee53ac1e50c9c75dc749886e3257bb8f

105919 --> testing fail

Test environment and result as below:

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

==== 20 line log output for Ubuntu 20.04 ARM GCC Native (abi_test): ====
type size hasn't changed
1 data member changes (1 filtered):
type of 'rte_mempool* rte_mbuf::pool' changed:
in pointed to type 'struct rte_mempool' at rte_mempool.h:213:1:
type size hasn't changed
1 data member changes (2 filtered):
type of 'rte_mempool_cache* rte_mempool::local_cache' changed:
in pointed to type 'struct rte_mempool_cache' at rte_mempool.h:89:1:
type size changed from 98816 to 66048 (in bits)
1 data member change:
type of 'void* rte_mempool_cache::objs[1536]' changed:
type name changed from 'void*[1536]' to 'void*[1024]'
array type size changed from 98304 to 65536
array type subrange 1 changed length from 1536 to 1024
and offset changed from 128 to 512 (in bits) (by +384 bits)

Error: ABI issue reported for 'abidiff --suppr dpdk/devtools/libabigail.abignore --no-added-syms --headers-dir1 /opt/dpdklab/abi_references/v21.11/armgigabyteref/include --headers-dir2 build_install/include /opt/dpdklab/abi_references/v21.11/armgigabyteref/dump/librte_distributor.dump build_install/dump/librte_distributor.dump'

ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).

==== End log output ====

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

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

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)

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 34 clang
	Kernel: 5.4.0-72-generic
	Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)

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

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 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)

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

Ubuntu 20.04 ARM GCC Native
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-01-17 15:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 15:26 dpdklab [this message]
     [not found] <20220117115231.8060-1-mb@smartsharesystems.com>
2022-01-17 11:52 ` 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=20220117152603.11378602B7@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=mb@smartsharesystems.com \
    --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).