automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: nicolas.chautru@intel.com, robot@bytheb.org
Subject: |FAILURE| pw139112 [PATCH v1 3/3] test/bbdev: update for queue stats
Date: Thu,  4 Apr 2024 18:04:25 -0400	[thread overview]
Message-ID: <20240404220425.169156-1-robot@bytheb.org> (raw)
In-Reply-To: <20240404210447.1915517-4-nicolas.chautru@intel.com>

From: robot@bytheb.org

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

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

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################

1 function with some indirect sub-type change:

  [C] 'function rte_bbdev* rte_bbdev_allocate(const char*)' at rte_bbdev.c:175:1 has some indirect sub-type changes:
    return type changed:
      in pointed to type 'struct rte_bbdev' at rte_bbdev.h:508:1:
        type size hasn't changed
        1 data member changes (13 filtered):
          type of 'rte_bbdev_enqueue_enc_ops_t enqueue_enc_ops' changed:
            underlying type 'typedef uint16_t (rte_bbdev_queue_data*, rte_bbdev_enc_op**, typedef uint16_t)*' changed:
              in pointed to type 'function type typedef uint16_t (rte_bbdev_queue_data*, rte_bbdev_enc_op**, typedef uint16_t)':
                parameter 1 of type 'rte_bbdev_queue_data*' has sub-type changes:
                  in pointed to type 'struct rte_bbdev_queue_data' at rte_bbdev.h:425:1:
                    type size changed from 1088 to 1152 (in bits)
                    3 data member changes:
                      type of 'rte_bbdev_stats queue_stats' changed:
                        type size changed from 832 to 896 (in bits)
                        1 data member insertion:
                          'uint16_t enqueue_depth_avail', at offset 832 (in bits) at rte_bbdev.h:287:1
                      'rte_bbdev_enqueue_status enqueue_status' offset changed from 1024 to 1088 (in bits) (by +64 bits)
                      'bool started' offset changed from 1056 to 1120 (in bits) (by +64 bits)

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_bbdev.so.24.1 install/usr/local/lib/librte_bbdev.so.24.2
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-22.04-gcc-abi+debug+doc+examples+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2024-04-04 22:04 UTC|newest]

Thread overview: 93+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240404210447.1915517-4-nicolas.chautru@intel.com>
2024-04-04 20:41 ` |SUCCESS| pw139111-139112 " qemudev
2024-04-04 20:45 ` qemudev
2024-04-04 21:05 ` |SUCCESS| pw139112 " checkpatch
2024-04-04 21:53 ` |SUCCESS| pw139111-139112 [PATCH] [v1,3/3] test/bbdev: update for qu dpdklab
2024-04-04 21:54 ` dpdklab
2024-04-04 21:55 ` dpdklab
2024-04-04 21:55 ` dpdklab
2024-04-04 21:56 ` dpdklab
2024-04-04 21:56 ` dpdklab
2024-04-04 21:57 ` dpdklab
2024-04-04 21:57 ` dpdklab
2024-04-04 21:57 ` dpdklab
2024-04-04 21:58 ` dpdklab
2024-04-04 22:01 ` dpdklab
2024-04-04 22:02 ` |WARNING| " dpdklab
2024-04-04 22:04 ` 0-day Robot [this message]
2024-04-04 22:07 ` dpdklab
2024-04-04 22:08 ` |SUCCESS| " dpdklab
2024-04-04 22:09 ` |WARNING| " dpdklab
2024-04-04 22:10 ` |SUCCESS| " dpdklab
2024-04-04 22:10 ` |FAILURE| " dpdklab
2024-04-04 22:11 ` |WARNING| " dpdklab
2024-04-04 22:11 ` dpdklab
2024-04-04 22:12 ` |SUCCESS| " dpdklab
2024-04-04 22:12 ` dpdklab
2024-04-04 22:13 ` dpdklab
2024-04-04 22:13 ` |WARNING| " dpdklab
2024-04-04 22:13 ` |FAILURE| " dpdklab
2024-04-04 22:14 ` |WARNING| " dpdklab
2024-04-04 22:14 ` dpdklab
2024-04-04 22:14 ` dpdklab
2024-04-04 22:15 ` dpdklab
2024-04-04 22:15 ` |SUCCESS| " dpdklab
2024-04-04 22:15 ` dpdklab
2024-04-04 22:15 ` |WARNING| " dpdklab
2024-04-04 22:16 ` |FAILURE| " dpdklab
2024-04-04 22:16 ` |WARNING| " dpdklab
2024-04-04 22:16 ` |FAILURE| " dpdklab
2024-04-04 22:16 ` |SUCCESS| " dpdklab
2024-04-04 22:20 ` |FAILURE| " dpdklab
2024-04-04 22:21 ` |SUCCESS| " dpdklab
2024-04-04 22:22 ` |FAILURE| " dpdklab
2024-04-04 22:22 ` |SUCCESS| " dpdklab
2024-04-04 22:23 ` dpdklab
2024-04-04 22:24 ` dpdklab
2024-04-04 22:24 ` |FAILURE| " dpdklab
2024-04-04 22:27 ` |SUCCESS| " dpdklab
2024-04-04 22:27 ` |FAILURE| " dpdklab
2024-04-04 22:27 ` |SUCCESS| " dpdklab
2024-04-04 22:29 ` dpdklab
2024-04-04 22:29 ` |FAILURE| " dpdklab
2024-04-04 22:32 ` |SUCCESS| " dpdklab
2024-04-04 22:33 ` dpdklab
2024-04-04 22:33 ` |FAILURE| " dpdklab
2024-04-04 22:34 ` |SUCCESS| " dpdklab
2024-04-04 22:34 ` |FAILURE| " dpdklab
2024-04-04 22:35 ` dpdklab
2024-04-04 22:36 ` |SUCCESS| " dpdklab
2024-04-04 22:37 ` |FAILURE| " dpdklab
2024-04-04 22:37 ` |SUCCESS| " dpdklab
2024-04-04 22:38 ` |FAILURE| " dpdklab
2024-04-04 22:39 ` |SUCCESS| " dpdklab
2024-04-04 22:45 ` |FAILURE| " dpdklab
2024-04-04 22:47 ` |SUCCESS| " dpdklab
2024-04-04 22:53 ` dpdklab
2024-04-04 23:01 ` dpdklab
2024-04-04 23:23 ` dpdklab
2024-04-04 23:37 ` dpdklab
2024-04-04 23:37 ` dpdklab
2024-04-04 23:40 ` dpdklab
2024-04-04 23:46 ` dpdklab
2024-04-04 23:59 ` dpdklab
2024-04-05  0:00 ` dpdklab
2024-04-05  0:03 ` dpdklab
2024-04-05  0:04 ` dpdklab
2024-04-05  0:07 ` dpdklab
2024-04-05  0:08 ` dpdklab
2024-04-05  0:10 ` dpdklab
2024-04-05  0:11 ` dpdklab
2024-04-05  0:13 ` dpdklab
2024-04-05  0:15 ` dpdklab
2024-04-05  0:30 ` dpdklab
2024-04-05  0:33 ` dpdklab
2024-04-05  0:38 ` dpdklab
2024-04-05  0:38 ` dpdklab
2024-04-05  0:41 ` dpdklab
2024-04-05  0:43 ` dpdklab
2024-04-05  0:58 ` dpdklab
2024-04-05  1:05 ` dpdklab
2024-04-05  1:06 ` dpdklab
2024-04-05  1:14 ` dpdklab
2024-04-05  1:38 ` dpdklab
2024-04-05  1:44 ` 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=20240404220425.169156-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=nicolas.chautru@intel.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).