automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: sthotton@marvell.com, robot@bytheb.org
Subject: [dpdk-test-report] |FAILURE| pw89908 [dpdk-dev] [PATCH v1 2/2] event/octeontx2: support crypto adapter forward mode
Date: Fri, 26 Mar 2021 06:57:23 -0400	[thread overview]
Message-ID: <20210326105723.27462-1-robot@bytheb.org> (raw)
In-Reply-To: <2ed9f23d6b7af4d1d366e8c883e64a9b8584063f.1616748930.git.sthotton@marvell.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=pw|patchwork.dpdk.org|build|15904|SHA|70ddc6a4034cea1d3e7ac240cbf3a67b95b5a5d3|passed|https://github.com/ovsrobot/dpdk/actions/runs/689562853|[dpdk-dev] [PATCH] doc: update limitations of OCTEON TX crypto PMDs|ovsrobot/dpdk, Size: 14352 bytes --]

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/689559996
Build Logs:
-----------------------Summary of failed steps-----------------------
ubuntu-18.04-gcc-static failed at step "Build and test"
ubuntu-18.04-gcc-shared-abi+doc+tests failed at step "Build and test"
ubuntu-18.04-clang-static failed at step "Build and test"
ubuntu-18.04-clang-shared-doc+tests failed at step "Build and test"
ubuntu-18.04-gcc-static-aarch64 failed at step "Build and test"
ubuntu-18.04-gcc-shared-aarch64 failed at step "Build and test"
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] ubuntu-18.04-gcc-static at step "Build and test"
####################################################################################
  union rte_event_crypto_metadata *m_data;
                                   ^~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:471:40: error: ‘m_data’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
        ((uint64_t)m_data->response_info.sched_type << 32) |
                   ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:445:35: note: ‘m_data’ was declared here
  union rte_event_crypto_metadata *m_data;
                                   ^~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:471:40: error: ‘m_data’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
        ((uint64_t)m_data->response_info.sched_type << 32) |
                   ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:445:35: note: ‘m_data’ was declared here
  union rte_event_crypto_metadata *m_data;
                                   ^~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:471:40: error: ‘m_data’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
        ((uint64_t)m_data->response_info.sched_type << 32) |
                   ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:445:35: note: ‘m_data’ was declared here
  union rte_event_crypto_metadata *m_data;
                                   ^~~~~~
cc1: all warnings being treated as errors
[2146/3183] Compiling C object 'drivers/drivers@@tmp_rte_crypto_octeontx@sta/crypto_octeontx_otx_cryptodev_ops.c.o'.
[2147/3183] Compiling C object 'drivers/drivers@@tmp_rte_crypto_openssl@sta/crypto_openssl_rte_openssl_pmd_ops.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] ubuntu-18.04-gcc-static at step "Build and test"
####################################################################################




####################################################################################
#### [Begin job log] ubuntu-18.04-gcc-shared-abi+doc+tests at step "Build and test"
####################################################################################
  union rte_event_crypto_metadata *m_data;
                                   ^~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:471:40: error: ‘m_data’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
        ((uint64_t)m_data->response_info.sched_type << 32) |
                   ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:445:35: note: ‘m_data’ was declared here
  union rte_event_crypto_metadata *m_data;
                                   ^~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:471:40: error: ‘m_data’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
        ((uint64_t)m_data->response_info.sched_type << 32) |
                   ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:445:35: note: ‘m_data’ was declared here
  union rte_event_crypto_metadata *m_data;
                                   ^~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:471:40: error: ‘m_data’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
        ((uint64_t)m_data->response_info.sched_type << 32) |
                   ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:445:35: note: ‘m_data’ was declared here
  union rte_event_crypto_metadata *m_data;
                                   ^~~~~~
cc1: all warnings being treated as errors
[2208/3399] Generating rte_crypto_openssl.pmd.c with a custom command.
[2209/3399] Linking target drivers/librte_crypto_octeontx.so.21.2.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] ubuntu-18.04-gcc-shared-abi+doc+tests at step "Build and test"
####################################################################################




####################################################################################
#### [Begin job log] ubuntu-18.04-clang-static at step "Build and test"
####################################################################################
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:470:9: note: uninitialized use occurs here
                      m_data->response_info.flow_id) |
                      ^~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:452:7: note: remove the 'if' if its condition is always true
        else if (op->sess_type == RTE_CRYPTO_OP_SESSIONLESS &&
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:452:11: error: variable 'm_data' is used uninitialized whenever '&&' condition is false [-Werror,-Wsometimes-uninitialized]
        else if (op->sess_type == RTE_CRYPTO_OP_SESSIONLESS &&
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:470:9: note: uninitialized use occurs here
                      m_data->response_info.flow_id) |
                      ^~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:452:11: note: remove the '&&' if its condition is always true
        else if (op->sess_type == RTE_CRYPTO_OP_SESSIONLESS &&
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:445:41: note: initialize the variable 'm_data' to silence this warning
        union rte_event_crypto_metadata *m_data;
                                               ^
                                                = NULL
2 errors generated.
[2136/3185] Compiling C object 'drivers/drivers@@tmp_rte_crypto_octeontx@sta/crypto_octeontx_otx_cryptodev_ops.c.o'.
[2137/3185] Compiling C object 'drivers/drivers@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_rxtx.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] ubuntu-18.04-clang-static at step "Build and test"
####################################################################################




####################################################################################
#### [Begin job log] ubuntu-18.04-clang-shared-doc+tests at step "Build and test"
####################################################################################
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:470:9: note: uninitialized use occurs here
                      m_data->response_info.flow_id) |
                      ^~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:452:7: note: remove the 'if' if its condition is always true
        else if (op->sess_type == RTE_CRYPTO_OP_SESSIONLESS &&
             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:452:11: error: variable 'm_data' is used uninitialized whenever '&&' condition is false [-Werror,-Wsometimes-uninitialized]
        else if (op->sess_type == RTE_CRYPTO_OP_SESSIONLESS &&
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:470:9: note: uninitialized use occurs here
                      m_data->response_info.flow_id) |
                      ^~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:452:11: note: remove the '&&' if its condition is always true
        else if (op->sess_type == RTE_CRYPTO_OP_SESSIONLESS &&
                 ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:445:41: note: initialize the variable 'm_data' to silence this warning
        union rte_event_crypto_metadata *m_data;
                                               ^
                                                = NULL
2 errors generated.
[2189/3401] Compiling C object 'drivers/drivers@@tmp_rte_crypto_octeontx@sta/crypto_octeontx_otx_cryptodev_ops.c.o'.
[2190/3401] Compiling C object 'drivers/drivers@@tmp_rte_net_mlx5@sta/net_mlx5_mlx5_rxtx.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] ubuntu-18.04-clang-shared-doc+tests at step "Build and test"
####################################################################################




####################################################################################
#### [Begin job log] ubuntu-18.04-gcc-static-aarch64 at step "Build and test"
####################################################################################
  union rte_event_crypto_metadata *m_data;
                                   ^~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:471:40: error: ‘m_data’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
        ((uint64_t)m_data->response_info.sched_type << 32) |
                   ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:445:35: note: ‘m_data’ was declared here
  union rte_event_crypto_metadata *m_data;
                                   ^~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:471:40: error: ‘m_data’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
        ((uint64_t)m_data->response_info.sched_type << 32) |
                   ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:445:35: note: ‘m_data’ was declared here
  union rte_event_crypto_metadata *m_data;
                                   ^~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:471:40: error: ‘m_data’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
        ((uint64_t)m_data->response_info.sched_type << 32) |
                   ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:445:35: note: ‘m_data’ was declared here
  union rte_event_crypto_metadata *m_data;
                                   ^~~~~~
cc1: all warnings being treated as errors
[2147/3183] Generating rte_crypto_openssl.pmd.c with a custom command.
[2148/3183] Compiling C object 'drivers/drivers@@tmp_rte_crypto_octeontx@sta/crypto_octeontx_otx_cryptodev_ops.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] ubuntu-18.04-gcc-static-aarch64 at step "Build and test"
####################################################################################




####################################################################################
#### [Begin job log] ubuntu-18.04-gcc-shared-aarch64 at step "Build and test"
####################################################################################
  union rte_event_crypto_metadata *m_data;
                                   ^~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:471:40: error: ‘m_data’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
        ((uint64_t)m_data->response_info.sched_type << 32) |
                   ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:445:35: note: ‘m_data’ was declared here
  union rte_event_crypto_metadata *m_data;
                                   ^~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:471:40: error: ‘m_data’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
        ((uint64_t)m_data->response_info.sched_type << 32) |
                   ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:445:35: note: ‘m_data’ was declared here
  union rte_event_crypto_metadata *m_data;
                                   ^~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:471:40: error: ‘m_data’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
        ((uint64_t)m_data->response_info.sched_type << 32) |
                   ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
../drivers/crypto/octeontx2/otx2_cryptodev_ops.c:445:35: note: ‘m_data’ was declared here
  union rte_event_crypto_metadata *m_data;
                                   ^~~~~~
cc1: all warnings being treated as errors
[2200/3396] Compiling C object 'drivers/drivers@@tmp_rte_crypto_octeontx@sta/crypto_octeontx_otx_cryptodev_ops.c.o'.
[2201/3396] Compiling C object 'drivers/drivers@@tmp_rte_crypto_scheduler@sta/crypto_scheduler_scheduler_failover.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] ubuntu-18.04-gcc-shared-aarch64 at step "Build and test"
####################################################################################
--------------------------------END LOGS-----------------------------

      parent reply	other threads:[~2021-03-26 10:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2ed9f23d6b7af4d1d366e8c883e64a9b8584063f.1616748930.git.sthotton@marvell.com>
2021-03-26  9:16 ` [dpdk-test-report] |SUCCESS| pw89908 " checkpatch
2021-03-26 10:55 ` [dpdk-test-report] |FAILURE| pw89908 " 0-day Robot
2021-03-26 10:57 ` 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=20210326105723.27462-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=sthotton@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).