From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: ciara.power@intel.com, robot@bytheb.org
Subject: |FAILURE| pw105110 [PATCH] crypto: use single buffer for asymmetric session
Date: Mon, 13 Dec 2021 10:38:29 -0500 [thread overview]
Message-ID: <20211213153829.31691-1-robot@bytheb.org> (raw)
In-Reply-To: <20211213150402.3351032-1-ciara.power@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/105110/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/1573567471
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-18.04-gcc-shared-abi+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-18.04-gcc-shared-abi+doc+tests" at step Build and test
####################################################################################
1 data member change:
type of 'rte_cryptodev_asym_session* session' changed:
in pointed to type 'struct rte_cryptodev_asym_session' at rte_cryptodev.h:922:1:
type size changed from 0 to 64 (in bits)
4 data member insertions:
'uint8_t rte_cryptodev_asym_session::driver_id', at offset 0 (in bits) at rte_cryptodev.h:923:1
'uint8_t rte_cryptodev_asym_session::max_priv_session_sz', at offset 8 (in bits) at rte_cryptodev.h:925:1
'uint16_t rte_cryptodev_asym_session::user_data_sz', at offset 16 (in bits) at rte_cryptodev.h:927:1
'uint8_t rte_cryptodev_asym_session::padding[4]', at offset 32 (in bits) at rte_cryptodev.h:929:1
1 data member change:
type of 'void* rte_cryptodev_asym_session::sess_private_data[]' changed:
array element type 'void*' changed:
entity changed from 'void*' to 'typedef uint8_t' at stdint-uintn.h:24:1
type size changed from 64 to 8 (in bits)
type name changed from 'void*[]' to 'uint8_t[]'
type size hasn't changed
and offset changed from 0 to 64 (in bits) (by +64 bits)
type size hasn't changed
type size hasn't changed
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_cryptodev.dump install/dump/librte_cryptodev.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-18.04-gcc-shared-abi+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
next prev parent reply other threads:[~2021-12-13 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211213150402.3351032-1-ciara.power@intel.com>
2021-12-13 15:05 ` |SUCCESS| " checkpatch
2021-12-13 15:38 ` 0-day Robot [this message]
2021-12-13 16:30 |FAILURE| " dpdklab
2021-12-13 16:51 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=20211213153829.31691-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=ciara.power@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).