From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: syaligar@marvell.com, robot@bytheb.org
Subject: |FAILURE| pw125563 [PATCH v1 1/1] cryptodev: support EDDSA
Date: Tue, 28 Mar 2023 07:38:52 -0400 [thread overview]
Message-ID: <20230328113852.2734549-1-robot@bytheb.org> (raw)
In-Reply-To: <20230328102052.30465-1-syaligar@marvell.com>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: FAILURE
http://patchwork.dpdk.org/patch/125563/
_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/4542122864
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-gcc-abi+debug+doc+tests" failed at step Build and test
----------------------End summary of failed steps--------------------
-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-gcc-abi+debug+doc+tests" at step Build and test
####################################################################################
type size hasn't changed
1 data member change:
type of 'rte_crypto_asym_xform_type xform_type' changed:
type size hasn't changed
1 enumerator insertion:
'rte_crypto_asym_xform_type::RTE_CRYPTO_ASYM_XFORM_EDDSA' value '8'
4 enumerator changes:
'rte_crypto_asym_xform_type::RTE_CRYPTO_ASYM_XFORM_ECDH' from value '8' to '9' at rte_crypto_asym.h:83:1
'rte_crypto_asym_xform_type::RTE_CRYPTO_ASYM_XFORM_ECPM' from value '9' to '10' at rte_crypto_asym.h:83:1
'rte_crypto_asym_xform_type::RTE_CRYPTO_ASYM_XFORM_ECFPM' from value '10' to '11' at rte_crypto_asym.h:83:1
'rte_crypto_asym_xform_type::RTE_CRYPTO_ASYM_XFORM_TYPE_LIST_END' from value '11' to '12' at rte_crypto_asym.h:83:1
Functions changes summary: 0 Removed, 0 Changed (34 filtered out), 0 Added (5 filtered out) functions
Variables changes summary: 0 Removed (6 filtered out), 0 Changed (1 filtered out), 0 Added variables
Functions changes summary: 0 Removed, 0 Changed, 0 Added (1 filtered out) function
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
Functions changes summary: 0 Removed (1 filtered out), 0 Changed (276 filtered out), 0 Added (42 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added (1 filtered out) variable
Functions changes summary: 0 Removed, 0 Changed (84 filtered out), 0 Added (12 filtered out) functions
Variables changes summary: 0 Removed, 0 Changed, 0 Added variable
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-gcc-abi+debug+doc+tests" at step Build and test
####################################################################################
--------------------------------END LOGS-----------------------------
prev parent reply other threads:[~2023-03-28 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230328102052.30465-1-syaligar@marvell.com>
2023-03-28 10:10 ` |SUCCESS| " qemudev
2023-03-28 10:14 ` qemudev
2023-03-28 10:22 ` |WARNING| " checkpatch
2023-03-28 11: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=20230328113852.2734549-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=syaligar@marvell.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).