From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: radu.nicolau@intel.com, robot@bytheb.org
Subject: [dpdk-test-report] |FAILURE| pw96906 [dpdk-dev] [PATCH v3 10/10] ipsec: add ol_flags support
Date: Fri, 13 Aug 2021 06:38:30 -0400 [thread overview]
Message-ID: <20210813103830.1536-1-robot@bytheb.org> (raw)
In-Reply-To: <20210813093019.785286-11-radu.nicolau@intel.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/96906/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/1127235948
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
####################################################################################
type of 'rte_security_ipsec_xform ipsec' changed:
type size changed from 704 to 832 (in bits)
3 data member insertions:
'rte_security_ipsec_udp_param rte_security_ipsec_xform::udp', at offset 576 (in bits) at rte_security.h:233:1
'uint32_t rte_security_ipsec_xform::mss', at offset 736 (in bits) at rte_security.h:241:1
'union {uint64_t value; struct {uint32_t low; uint32_t hi;};} rte_security_ipsec_xform::esn', at offset 768 (in bits) at rte_security.h:249:1
3 data member changes:
'rte_security_ipsec_sa_options rte_security_ipsec_xform::options' has *some* difference - please report as a bug
'uint64_t rte_security_ipsec_xform::esn_soft_limit' offset changed from 576 to 640 (in bits) (by +64 bits)
'uint32_t rte_security_ipsec_xform::replay_win_sz' offset changed from 640 to 704 (in bits) (by +64 bits)
'rte_crypto_sym_xform* rte_security_session_conf::crypto_xform' offset changed from 768 to 896 (in bits) (by +128 bits)
'void* rte_security_session_conf::userdata' offset changed from 832 to 960 (in bits) (by +128 bits)
Functions changes summary: 0 Removed, 0 Changed (2 filtered out), 0 Added (1 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Functions changes summary: 0 Removed, 0 Changed (33 filtered out), 0 Added functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Functions changes summary: 0 Removed, 0 Changed (54 filtered out), 0 Added (11 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
##[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-----------------------------
prev parent reply other threads:[~2021-08-13 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210813093019.785286-11-radu.nicolau@intel.com>
2021-08-13 9:47 ` [dpdk-test-report] |SUCCESS| pw96906 " checkpatch
2021-08-13 10:38 ` 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=20210813103830.1536-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=radu.nicolau@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).