automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: mb@smartsharesystems.com, robot@bytheb.org
Subject: |FAILURE| pw120489 [PATCH v8] mbuf perf test, please ignore
Date: Tue,  6 Dec 2022 09:39:55 -0500	[thread overview]
Message-ID: <20221206143955.1114328-1-robot@bytheb.org> (raw)
In-Reply-To: <20221206121630.63390-1-mb@smartsharesystems.com>

From: robot@bytheb.org

Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/120489/

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/3629474013
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-abi+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-abi+doc+tests" at step Build and test
####################################################################################
Functions changes summary: 0 Removed, 1 Changed (6 filtered out), 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

1 function with some indirect sub-type change:

  [C] 'function unsigned int rte_reorder_drain(rte_reorder_buffer*, rte_mbuf**, unsigned int)' at rte_reorder.c:381:1 has some indirect sub-type changes:
    parameter 2 of type 'rte_mbuf**' has sub-type changes:
      in pointed to type 'rte_mbuf*':
        in pointed to type 'struct rte_mbuf' at rte_mbuf_core.h:465:1:
          type size hasn't changed
          2 data member changes (1 filtered):
            'rte_mempool* pool' offset changed from 448 to 576 (in bits) (by +128 bits)
            while looking at anonymous data member 'union {uint64_t tx_offload; struct {uint64_t l2_len; uint64_t l3_len; uint64_t l4_len; uint64_t tso_segsz; uint64_t outer_l3_len; uint64_t outer_l2_len;};}':
            the internal name of that anonymous data member changed from:
             __anonymous_union__7
            to:
             __anonymous_union__5
             This is usually due to an anonymous member type being added or removed from the containing type
            and offset changed from 576 to 448 (in bits) (by -128 bits)

Error: ABI issue reported for 'abidiff --suppr devtools/libabigail.abignore --no-added-syms --headers-dir1 reference/usr/local/include --headers-dir2 install/usr/local/include reference/dump/librte_reorder.dump install/dump/librte_reorder.dump'
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).


##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-abi+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2022-12-06 14:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221206121630.63390-1-mb@smartsharesystems.com>
2022-12-06 12:18 ` |SUCCESS| " checkpatch
2022-12-06 14:39 ` 0-day Robot [this message]
2022-12-08 16:28 ` qemudev
2022-12-08 16:29 ` qemudev
2022-12-08 17:04 ` qemudev
2022-12-08 17:05 ` qemudev
2022-12-09  4:21 ` qemudev
2022-12-09  4:21 ` qemudev
2022-12-10  0:53 ` qemudev
2022-12-10  0:54 ` qemudev
2022-12-06 16:07 |FAILURE| pw120489 [PATCH] [v8] " dpdklab
2022-12-06 16:08 dpdklab
2022-12-06 16:08 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=20221206143955.1114328-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --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).