automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: roretzla@linux.microsoft.com, robot@bytheb.org
Subject: |FAILURE| pw136620 [PATCH v2 4/4] pipeline: replace zero length array with flex array
Date: Mon, 12 Feb 2024 18:44:30 -0500	[thread overview]
Message-ID: <20240212234430.2368433-1-robot@bytheb.org> (raw)
In-Reply-To: <1707777366-26000-5-git-send-email-roretzla@linux.microsoft.com>

From: robot@bytheb.org

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

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

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

Functions changes summary: 0 Removed, 1 Changed (123 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 int rte_pipeline_table_create(rte_pipeline*, rte_pipeline_table_params*, uint32_t*)' at rte_pipeline.c:322:1 has some indirect sub-type changes:
    parameter 2 of type 'rte_pipeline_table_params*' has sub-type changes:
      in pointed to type 'struct rte_pipeline_table_params' at rte_pipeline.h:301:1:
        type size hasn't changed
        1 data member changes (1 filtered):
          type of 'rte_pipeline_table_action_handler_hit f_action_hit' changed:
            underlying type 'int (rte_pipeline*, rte_mbuf**, typedef uint64_t, rte_pipeline_table_entry**, void*)*' changed:
              in pointed to type 'function type int (rte_pipeline*, rte_mbuf**, typedef uint64_t, rte_pipeline_table_entry**, void*)':
                parameter 4 of type 'rte_pipeline_table_entry**' has sub-type changes:
                  in pointed to type 'rte_pipeline_table_entry*':
Error: ABI issue reported for abidiff --suppr /home/runner/work/dpdk/dpdk/devtools/libabigail.abignore --no-added-syms --headers-dir1 reference/usr/local/include --headers-dir2 install/usr/local/include reference/usr/local/lib/librte_pipeline.so.24.0 install/usr/local/lib/librte_pipeline.so.24.1
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).
                    in pointed to type 'struct rte_pipeline_table_entry' at rte_pipeline.h:211:1:
                      type size hasn't changed
                      1 data member change:
                        'uint8_t action_data[]' has *some* difference - please report as a bug

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

      parent reply	other threads:[~2024-02-12 23:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1707777366-26000-5-git-send-email-roretzla@linux.microsoft.com>
2024-02-12 22:19 ` |SUCCESS| pw136621-136620 " qemudev
2024-02-12 22:24 ` qemudev
2024-02-12 22:36 ` |SUCCESS| pw136620 " checkpatch
2024-02-12 23:44 ` 0-day Robot [this message]

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=20240212234430.2368433-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=roretzla@linux.microsoft.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).