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, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |WARNING| [GIT MASTER] 0f80c13b4d589f63a8ede56bea0a443750bdcc47
Date: Fri,  5 Aug 2022 06:05:00 +0000 (UTC)	[thread overview]
Message-ID: <20220805060500.D4DD5600E7@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

_Testing issues_

Branch: tags/v21.11

0f80c13b4d589f63a8ede56bea0a443750bdcc47 --> testing fail

Test environment and result as below:

+-----------------------------+----------+
|         Environment         | abi_test |
+=============================+==========+
| RHEL8                       | FAIL     |
+-----------------------------+----------+
| Ubuntu 20.04 ARM GCC Native | PASS     |
+-----------------------------+----------+
| RHEL 7                      | FAIL     |
+-----------------------------+----------+
| Fedora 34 clang             | FAIL     |
+-----------------------------+----------+

==== 20 line log output for Fedora 34 clang (abi_test): ====
'uint16_t attr_valid' offset changed from 15 to 31 (in bits) (by +16 bits)

[C] 'function int rte_event_dev_stop_flush_callback_register(uint8_t, eventdev_stop_flush_t, void*)' at rte_eventdev.c:1259:1 has some indirect sub-type changes:
parameter 2 of type 'typedef eventdev_stop_flush_t' has sub-type changes:
underlying type 'void (typedef uint8_t, struct rte_event, void*)*' changed:
in pointed to type 'function type void (typedef uint8_t, struct rte_event, void*)':
parameter 2 of type 'struct rte_event' has sub-type changes:
details were reported earlier

[C] 'function rte_event_timer_adapter* rte_event_timer_adapter_create(const rte_event_timer_adapter_conf*)' at rte_event_timer_adapter.c:122:1 has some indirect sub-type changes:
return type changed:
in pointed to type 'struct rte_event_timer_adapter' at rte_event_timer_adapter.h:517:1:
type size hasn't changed
1 data member changes (5 filtered):
'uint8_t allocated' offset changed from 0 to 320 (in bits) (by +320 bits)

Error: ABI issue reported for 'abidiff --suppr dpdk/devtools/libabigail.abignore --no-added-syms --headers-dir1 reference/include --headers-dir2 build_install/include reference/dump/librte_eventdev.dump build_install/dump/librte_eventdev.dump'

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

==== End log output ====

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

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

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 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/tarballs/20974/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-08-05  6:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-05  6:05 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-08  5:48 dpdklab
2022-08-07  5:51 dpdklab
2022-08-06  5:51 dpdklab
2022-08-04  6:07 dpdklab
2022-08-04  5:42 dpdklab
2022-08-03  6:05 dpdklab
2022-08-02  6:13 dpdklab
2022-08-01  6:14 dpdklab
2022-07-31  5:54 dpdklab
2022-07-30  6:04 dpdklab
2022-07-29  6:18 dpdklab

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=20220805060500.D4DD5600E7@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).