automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: stephen@networkplumber.org, robot@bytheb.org
Subject: |FAILURE| pw148429 [RFC 5/5] test: remove unneeded memset
Date: Wed, 13 Nov 2024 14:45:19 -0500	[thread overview]
Message-ID: <20241113194519.1510135-1-robot@bytheb.org> (raw)
In-Reply-To: <20241113185720.28706-6-stephen@networkplumber.org>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/11824123176
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-22.04-gcc-stdatomic" failed at step Build and test
"ubuntu-22.04-clang-stdatomic" failed at step Build and test
"ubuntu-22.04-gcc-debug+doc+examples+tests" failed at step Build and test
"ubuntu-22.04-clang-asan+doc+tests" failed at step Build and test
"fedora:39-gcc" failed at step Build
"fedora:39-clang" failed at step Build
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-stdatomic" at step Build and test
####################################################################################
[1168/3145] Linking static target drivers/libtmp_rte_net_bnx2x.a
[1169/3145] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_asym.c.o
FAILED: drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_asym.c.o 
ccache gcc -Idrivers/libtmp_rte_common_qat.a.p -Idrivers -I../drivers -Idrivers/common/qat -I../drivers/common/qat -I../drivers/common/qat/qat_adf -I../drivers/crypto/qat -I../drivers/compress/qat -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include -I../kernel/linux -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/pci -I../lib/pci -Ilib/cryptodev -I../lib/cryptodev -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/rcu -I../lib/rcu -Ilib/net -I../lib/net -Ilib/compressdev -I../lib/compressdev -Ilib/security -I../lib/security -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O2 -g -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=corei7 -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -Wno-address-of-packed-member -DBUILD_QAT_SYM -DBUILD_QAT_ASYM -DRTE_LOG_DEFAULT_LOGTYPE=pmd.common.qat -MD -MQ drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_asym.c.o -MF drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_asym.c.o.d -o drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_asym.c.o -c ../drivers/crypto/qat/qat_asym.c
../drivers/crypto/qat/qat_asym.c: In function ‘session_clear_modexp’:
../drivers/crypto/qat/qat_asym.c:106:17: error: implicit declaration of function ‘memset_s’; did you mean ‘memset’? [-Werror=implicit-function-declaration]
  106 |                 memset_s(what.data, 0, what.length); \
      |                 ^~~~~~~~
../drivers/crypto/qat/qat_asym.c:1453:9: note: in expansion of macro ‘PARAM_CLR’
 1453 |         PARAM_CLR(modex->modulus);
      |         ^~~~~~~~~
../drivers/crypto/qat/qat_asym.c:106:17: error: nested extern declaration of ‘memset_s’ [-Werror=nested-externs]
  106 |                 memset_s(what.data, 0, what.length); \
      |                 ^~~~~~~~
../drivers/crypto/qat/qat_asym.c:1453:9: note: in expansion of macro ‘PARAM_CLR’
 1453 |         PARAM_CLR(modex->modulus);
      |         ^~~~~~~~~
cc1: all warnings being treated as errors
[1170/3145] Generating rte_net_bnx2x.pmd.c with a custom command
[1171/3145] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_irq.c.o
[1172/3145] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_ring.c.o
[1173/3145] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_txr.c.o
[1174/3145] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_hwrm.c.o
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-stdatomic" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-stdatomic" at step Build and test
####################################################################################
                PARAM_CLR(rsa->qt.dP);
                ^
../drivers/crypto/qat/qat_asym.c:106:3: note: expanded from macro 'PARAM_CLR'
                memset_s(what.data, 0, what.length); \
                ^
../drivers/crypto/qat/qat_asym.c:1474:3: error: implicit declaration of function 'memset_s' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
                PARAM_CLR(rsa->qt.dQ);
                ^
../drivers/crypto/qat/qat_asym.c:106:3: note: expanded from macro 'PARAM_CLR'
                memset_s(what.data, 0, what.length); \
                ^
../drivers/crypto/qat/qat_asym.c:1475:3: error: implicit declaration of function 'memset_s' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
                PARAM_CLR(rsa->qt.qInv);
                ^
../drivers/crypto/qat/qat_asym.c:106:3: note: expanded from macro 'PARAM_CLR'
                memset_s(what.data, 0, what.length); \
                ^
11 errors generated.
[876/3145] Generating rte_common_mlx5.sym_chk with a custom command (wrapped by meson to capture output)
[877/3145] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_crypto.c.o
[878/3145] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_sym_session.c.o
[879/3145] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[880/3145] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_table_action.c.o
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-clang-stdatomic" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-22.04-gcc-debug+doc+examples+tests" at step Build and test
####################################################################################
[936/6569] Compiling C object drivers/common/sfc_efx/base/libsfc_base.a.p/siena_nvram.c.o
[937/6569] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_asym.c.o
FAILED: drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_asym.c.o 
ccache gcc -Idrivers/libtmp_rte_common_qat.a.p -Idrivers -I../drivers -Idrivers/common/qat -I../drivers/common/qat -I../drivers/common/qat/qat_adf -I../drivers/crypto/qat -I../drivers/compress/qat -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/x86/include -I../lib/eal/x86/include -I../kernel/linux -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/pci -I../lib/pci -Ilib/cryptodev -I../lib/cryptodev -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Ilib/rcu -I../lib/rcu -Ilib/net -I../lib/net -Ilib/compressdev -I../lib/compressdev -Ilib/security -I../lib/security -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -g -include rte_config.h -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=corei7 -mrtm -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -Wno-address-of-packed-member -DBUILD_QAT_SYM -DBUILD_QAT_ASYM -DRTE_LOG_DEFAULT_LOGTYPE=pmd.common.qat -MD -MQ drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_asym.c.o -MF drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_asym.c.o.d -o drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_asym.c.o -c ../drivers/crypto/qat/qat_asym.c
../drivers/crypto/qat/qat_asym.c: In function ‘session_clear_modexp’:
../drivers/crypto/qat/qat_asym.c:106:17: error: implicit declaration of function ‘memset_s’; did you mean ‘memset’? [-Werror=implicit-function-declaration]
  106 |                 memset_s(what.data, 0, what.length); \
      |                 ^~~~~~~~
../drivers/crypto/qat/qat_asym.c:1453:9: note: in expansion of macro ‘PARAM_CLR’
 1453 |         PARAM_CLR(modex->modulus);
      |         ^~~~~~~~~
../drivers/crypto/qat/qat_asym.c:106:17: error: nested extern declaration of ‘memset_s’ [-Werror=nested-externs]
  106 |                 memset_s(what.data, 0, what.length); \
      |                 ^~~~~~~~
../drivers/crypto/qat/qat_asym.c:1453:9: note: in expansion of macro ‘PARAM_CLR’
 1453 |         PARAM_CLR(modex->modulus);
      |         ^~~~~~~~~
cc1: all warnings being treated as errors
[938/6569] Compiling C object drivers/common/sfc_efx/base/libsfc_base.a.p/siena_phy.c.o
[939/6569] Compiling C object drivers/common/sfc_efx/base/libsfc_base.a.p/siena_vpd.c.o
[940/6569] Compiling C object drivers/common/sfc_efx/base/libsfc_base.a.p/ef10_evb.c.o
[941/6569] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_table_action.c.o
[942/6569] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-gcc-debug+doc+examples+tests" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################
                PARAM_CLR(rsa->qt.dP);
                ^
../drivers/crypto/qat/qat_asym.c:106:3: note: expanded from macro 'PARAM_CLR'
                memset_s(what.data, 0, what.length); \
                ^
../drivers/crypto/qat/qat_asym.c:1474:3: error: implicit declaration of function 'memset_s' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
                PARAM_CLR(rsa->qt.dQ);
                ^
../drivers/crypto/qat/qat_asym.c:106:3: note: expanded from macro 'PARAM_CLR'
                memset_s(what.data, 0, what.length); \
                ^
../drivers/crypto/qat/qat_asym.c:1475:3: error: implicit declaration of function 'memset_s' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
                PARAM_CLR(rsa->qt.qInv);
                ^
../drivers/crypto/qat/qat_asym.c:106:3: note: expanded from macro 'PARAM_CLR'
                memset_s(what.data, 0, what.length); \
                ^
11 errors generated.
[887/6569] Generating rte_common_mlx5.sym_chk with a custom command (wrapped by meson to capture output)
[888/6569] Compiling C object drivers/libtmp_rte_common_qat.a.p/compress_qat_qat_comp.c.o
[889/6569] Compiling C object drivers/libtmp_rte_common_qat.a.p/crypto_qat_qat_sym_session.c.o
[890/6569] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[891/6569] Compiling C object lib/librte_vhost.a.p/vhost_virtio_net.c.o
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-22.04-clang-asan+doc+tests" at step Build and test
####################################################################################




####################################################################################
#### [Begin job log] "fedora:39-gcc" at step Build
####################################################################################
####################################################################################
#### [End job log] "fedora:39-gcc" at step Build
####################################################################################




####################################################################################
#### [Begin job log] "fedora:39-clang" at step Build
####################################################################################
####################################################################################
#### [End job log] "fedora:39-clang" at step Build
####################################################################################
--------------------------------END LOGS-----------------------------

  parent reply	other threads:[~2024-11-13 19:45 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241113185720.28706-6-stephen@networkplumber.org>
2024-11-13 18:28 ` |FAILURE| pw148425-148429 " qemudev
2024-11-13 18:59 ` |SUCCESS| pw148429 " checkpatch
2024-11-13 19:45 ` 0-day Robot [this message]
2024-11-13 21:00 ` |SUCCESS| pw148425-148429 [PATCH] [RFC,5/5] test: remove unneeded me dpdklab
2024-11-13 21:57 ` dpdklab
2024-11-13 22:58 ` dpdklab
2024-11-13 23:28 ` dpdklab
2024-11-13 23:59 ` |FAILURE| " dpdklab
2024-11-14  0:12 ` |WARNING| " dpdklab
2024-11-14  0:12 ` dpdklab
2024-11-14  0:31 ` |PENDING| " dpdklab
2024-11-14  0:49 ` |FAILURE| " dpdklab
2024-11-14  0:50 ` dpdklab
2024-11-14  0:52 ` dpdklab
2024-11-14  0:53 ` dpdklab
2024-11-14  0:54 ` |PENDING| " dpdklab
2024-11-14  0:54 ` |FAILURE| " dpdklab
2024-11-14  0:56 ` dpdklab
2024-11-14  0:59 ` dpdklab
2024-11-14  0:59 ` dpdklab
2024-11-14  0:59 ` dpdklab
2024-11-14  1:00 ` dpdklab
2024-11-14  1:00 ` dpdklab
2024-11-14  1:01 ` dpdklab
2024-11-14  1:01 ` dpdklab
2024-11-14  1:01 ` dpdklab
2024-11-14  1:01 ` dpdklab
2024-11-14  1:02 ` dpdklab
2024-11-14  1:02 ` |WARNING| " dpdklab
2024-11-14  1:03 ` dpdklab
2024-11-14  1:18 ` dpdklab
2024-11-14  1:18 ` dpdklab
2024-11-14  1:39 ` dpdklab
2024-11-14  2:02 ` |FAILURE| " dpdklab
2024-11-14  2:03 ` dpdklab
2024-11-14  2:04 ` dpdklab
2024-11-14  2:06 ` dpdklab
2024-11-14  2:21 ` |PENDING| " dpdklab
2024-11-14  2:22 ` |WARNING| " dpdklab
2024-11-14  2:23 ` dpdklab
2024-11-14  2:59 ` |FAILURE| " dpdklab
2024-11-14  3:07 ` dpdklab
2024-11-14  3:23 ` dpdklab
2024-11-14  3:23 ` dpdklab
2024-11-14  3:44 ` |WARNING| " dpdklab
2024-11-14  3:45 ` dpdklab
2024-11-14  4:24 ` |FAILURE| " dpdklab
2024-11-14  4:28 ` 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=20241113194519.1510135-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=stephen@networkplumber.org \
    --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).