automatic DPDK test reports
 help / color / mirror / Atom feed
From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: gmuthukrishn@marvell.com, robot@bytheb.org
Subject: |FAILURE| pw131844 [PATCH] app/test: add modexp group tests
Date: Sat, 23 Sep 2023 08:27:04 -0400	[thread overview]
Message-ID: <20230923122704.1537867-1-robot@bytheb.org> (raw)
In-Reply-To: <20230923112005.308-1-gmuthukrishn@marvell.com>

From: robot@bytheb.org

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

_github build: failed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/6283398499
Build Logs:
-----------------------Summary of failed steps-----------------------
"ubuntu-20.04-clang-asan+doc+tests" failed at step Build and test
"fedora:37-clang" failed at step Build
----------------------End summary of failed steps--------------------

-------------------------------BEGIN LOGS----------------------------
####################################################################################
#### [Begin job log] "ubuntu-20.04-clang-asan+doc+tests" at step Build and test
####################################################################################
[2662/3814] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_crc.c.o'.
[2663/3814] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_cpuflags.c.o'.
[2664/3814] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_compressdev.c.o'.
[2665/3814] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_distributor_perf.c.o'.
[2666/3814] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_cycles.c.o'.
[2667/3814] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_cryptodev_asym.c.o'.
FAILED: app/a172ced@@dpdk-test@exe/test_test_cryptodev_asym.c.o 
ccache clang -Iapp/a172ced@@dpdk-test@exe -Iapp -I../app -Ilib/cmdline -I../lib/cmdline -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 -Ilib/eal/common -I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log -Ilib/telemetry/../metrics -I../lib/telemetry/../metrics -Ilib/telemetry -I../lib/telemetry -Ilib/net -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/ring -I../lib/ring -Idrivers/net/ring -I../drivers/net/ring -Ilib/ethdev -I../lib/ethdev -Ilib/meter -I../lib/meter -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/pci -I../lib/pci -Idrivers/bus/vdev -I../drivers/bus/vdev -Ilib/acl -I../lib/acl -Ilib/hash -I../lib/hash -Ilib/rcu -I../lib/rcu -Ilib/metrics -I../lib/metrics -Ilib/bitratestats -I../lib/bitratestats -Ilib/bpf -I../lib/bpf -Ilib/compressdev -I../lib/compressdev -Ilib/cryptodev -I../lib/cryptodev -Idrivers/crypto/scheduler -I../drivers/crypto/scheduler -Ilib/reorder -I../lib/reorder -Ilib/security -I../lib/security -Ilib/distributor -I../lib/distributor -Ilib/dmadev -I../lib/dmadev -Ilib/efd -I../lib/efd -Ilib/eventdev -I../lib/eventdev -Ilib/timer -I../lib/timer -Ilib/fib -I../lib/fib -Ilib/rib -I../lib/rib -Ilib/table -I../lib/table -Ilib/port -I../lib/port -Ilib/sched -I../lib/sched -Ilib/ip_frag -I../lib/ip_frag -Ilib/lpm -I../lib/lpm -Ilib/graph -I../lib/graph -Ilib/pcapng -I../lib/pcapng -Ilib/ipsec -I../lib/ipsec -Ilib/latencystats -I../lib/latencystats -Idrivers/net/bonding -I../drivers/net/bonding -Ilib/member -I../lib/member -Ilib/pdcp -I../lib/pdcp -Ilib/pdump -I../lib/pdump -Ilib/power -I../lib/power -Ilib/rawdev -I../lib/rawdev -Ilib/stack -I../lib/stack -Ilib/pipeline -I../lib/pipeline -Xclang -fcolor-diagnostics -fsanitize=address -fno-omit-frame-pointer -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-address-of-packed-member -Wno-missing-field-initializers -D_GNU_SOURCE -march=corei7 -mrtm -DALLOW_EXPERIMENTAL_API -fno-strict-aliasing -DALLOW_INTERNAL_API -MD -MQ 'app/a172ced@@dpdk-test@exe/test_test_cryptodev_asym.c.o' -MF 'app/a172ced@@dpdk-test@exe/test_test_cryptodev_asym.c.o.d' -o 'app/a172ced@@dpdk-test@exe/test_test_cryptodev_asym.c.o' -c ../app/test/test_cryptodev_asym.c
../app/test/test_cryptodev_asym.c:2702:30: error: initializer element is not a compile-time constant
                        modex_group_test_cases[0].description,
                        ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
../app/test/test.h:133:38: note: expanded from macro 'TEST_CASE_NAMED_WITH_DATA'
                { setup, teardown, NULL, testcase, name, 1, data }
                                                   ^~~~
../app/test/test_cryptodev_asym.c:2777:30: error: initializer element is not a compile-time constant
                        modex_group_test_cases[0].description,
                        ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~
../app/test/test.h:133:38: note: expanded from macro 'TEST_CASE_NAMED_WITH_DATA'
                { setup, teardown, NULL, testcase, name, 1, data }
                                                   ^~~~
2 errors generated.
[2668/3814] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_distributor.c.o'.
[2669/3814] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_cryptodev.c.o'.
ninja: build stopped: subcommand failed.
##[error]Process completed with exit code 1.
####################################################################################
#### [End job log] "ubuntu-20.04-clang-asan+doc+tests" at step Build and test
####################################################################################




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

  parent reply	other threads:[~2023-09-23 12:27 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230923112005.308-1-gmuthukrishn@marvell.com>
2023-09-23 11:01 ` |SUCCESS| " qemudev
2023-09-23 11:05 ` qemudev
2023-09-23 11:21 ` checkpatch
2023-09-23 12:27 ` 0-day Robot [this message]
2023-09-23 13:34 |FAILURE| " dpdklab
  -- strict thread matches above, loose matches on Subject: below --
2023-09-23 13:19 dpdklab
2023-09-23 13:08 dpdklab
2023-09-23 12:42 dpdklab
2023-09-23 12:26 dpdklab
2023-09-23 12:23 dpdklab
2023-09-23 12:21 dpdklab
2023-09-23 12:19 dpdklab
2023-09-23 12:16 dpdklab
2023-09-23 12:15 dpdklab
2023-09-23 12:15 dpdklab
2023-09-23 12:05 dpdklab
2023-09-23 12:05 dpdklab
2023-09-23 12:03 dpdklab
2023-09-23 12:03 dpdklab
2023-09-23 12:02 dpdklab
2023-09-23 12:02 dpdklab
2023-09-23 12:01 dpdklab
2023-09-23 12:01 dpdklab
2023-09-23 12:01 dpdklab
2023-09-23 12:01 dpdklab
2023-09-23 12:01 dpdklab
2023-09-23 12:00 dpdklab
2023-09-23 12:00 dpdklab
2023-09-23 12:00 dpdklab
2023-09-23 12:00 dpdklab
2023-09-23 12:00 dpdklab
2023-09-23 11:59 dpdklab
2023-09-23 11:58 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=20230923122704.1537867-1-robot@bytheb.org \
    --to=robot@bytheb.org \
    --cc=gmuthukrishn@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).