automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	"Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
Subject: |WARNING| pw112066-112077 [PATCH] [v3, 12/12] cryptodev: add salt length and optional label
Date: Thu,  2 Jun 2022 03:48:01 +0000 (UTC)	[thread overview]
Message-ID: <20220602034801.7641860093@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2244 bytes --]

Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/112077

_Testing issues_

Submitter: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
Date: Monday, May 30 2022 14:31:59 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:64fcadeac0f70c8c9c215196a3d580b4ad37dcdc

112066-112077 --> testing fail

Test environment and result as below:

+-----------------------------+----------+
|         Environment         | abi_test |
+=============================+==========+
| Ubuntu 20.04 ARM GCC Native | FAIL     |
+-----------------------------+----------+

==== 20 line log output for Ubuntu 20.04 ARM GCC Native (abi_test): ====
type size hasn't changed
1 data member change:
type of 'rte_crypto_asym_xform_type rte_cryptodev_asymmetric_xform_capability::xform_type' changed:
type size hasn't changed
1 enumerator insertion:
'rte_crypto_asym_xform_type::RTE_CRYPTO_ASYM_XFORM_ECDH' value '8'
2 enumerator changes:
'rte_crypto_asym_xform_type::RTE_CRYPTO_ASYM_XFORM_ECPM' from value '8' to '9' at rte_crypto_asym.h:80:1
'rte_crypto_asym_xform_type::RTE_CRYPTO_ASYM_XFORM_TYPE_LIST_END' from value '9' to '10' at rte_crypto_asym.h:80:1

Error: ABI issue reported for 'abidiff --suppr dpdk/devtools/libabigail.abignore --no-added-syms --headers-dir1 /opt/dpdklab/abi_references/v22.03/armgigabyteref/include --headers-dir2 build_install/include /opt/dpdklab/abi_references/v22.03/armgigabyteref/dump/librte_security.dump build_install/dump/librte_security.dump'

ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).

Functions changes summary: 0 Removed, 0 Changed (4 filtered out), 0 Added (2 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added variable

Functions changes summary: 0 Removed, 0 Changed (1 filtered out), 0 Added function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable

==== End log output ====

Ubuntu 20.04 ARM GCC Native
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/22359/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2022-06-02  3:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02  3:48 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-05-31  2:32 dpdklab
2022-05-30 19:11 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=20220602034801.7641860093@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=arkadiuszx.kusztal@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).