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,
	Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Subject: |FAILURE| pw133340 [PATCH] [v2] test/cryptodev: add modexp group tes
Date: Thu, 26 Oct 2023 00:40:28 -0700 (PDT)	[thread overview]
Message-ID: <653a17ec.020a0220.76143.35dbSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/133340

_Testing issues_

Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Thursday, October 26 2023 03:58:28 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2a0557d1ea21c3f63a212385348c97c414970e81

133340 --> testing fail

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | FAIL           |
+---------------------+----------------+
| CentOS Stream 9     | PASS           |
+---------------------+----------------+
| CentOS Stream 8     | PASS           |
+---------------------+----------------+
| Debian Buster       | PASS           |
+---------------------+----------------+
| Fedora 38           | FAIL           |
+---------------------+----------------+
| Fedora 37           | PASS           |
+---------------------+----------------+
| Debian Bullseye     | PASS           |
+---------------------+----------------+
| openSUSE Leap 15    | FAIL           |
+---------------------+----------------+
| Ubuntu 20.04        | PASS           |
+---------------------+----------------+

==== 20 line log output for openSUSE Leap 15 (dpdk_unit_test): ====
^
../app/test/test.h:134:38: note: in definition of macro 'TEST_CASE_NAMED_WITH_DATA'
{ setup, teardown, NULL, testcase, name, 1, data }
^~~~
../app/test/test_cryptodev_asym.c:2844:4: error: initializer element is not constant
modex_group_test_cases[5].description,
^
../app/test/test.h:134:38: note: in definition of macro 'TEST_CASE_NAMED_WITH_DATA'
{ setup, teardown, NULL, testcase, name, 1, data }
^~~~
../app/test/test_cryptodev_asym.c:2844:4: note: (near initialization for 'cryptodev_octeontx_asym_testsuite.unit_test_cases[9].name')
modex_group_test_cases[5].description,
^
../app/test/test.h:134:38: note: in definition of macro 'TEST_CASE_NAMED_WITH_DATA'
{ setup, teardown, NULL, testcase, name, 1, data }
^~~~
[2605/2722] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_event_eth_tx_adapter.c.o'.
[2606/2722] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_event_ring.c.o'.
[2607/2722] Compiling C object 'app/a172ced@@dpdk-test@exe/test_test_graph_perf.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

CentOS Stream 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

Fedora 38
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

Ubuntu 20.04
	Kernel: 5.4.0-153-generic
	Compiler: gcc 9.4.0-1ubuntu1~20.04.1

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-10-26  7:40 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26  7:40 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-26  8:22 dpdklab
2023-10-26  7:59 dpdklab
2023-10-26  7:49 dpdklab
2023-10-26  7:49 dpdklab
2023-10-26  7:49 dpdklab
2023-10-26  7:49 dpdklab
2023-10-26  7:48 dpdklab
2023-10-26  7:44 dpdklab
2023-10-26  7:41 dpdklab
2023-10-26  7:39 dpdklab
2023-10-26  7:39 dpdklab
2023-10-26  7:24 dpdklab
2023-10-26  7:23 dpdklab
2023-10-26  7:23 dpdklab
2023-10-26  7:19 dpdklab
2023-10-26  7:19 dpdklab
2023-10-26  7:18 dpdklab
2023-10-26  7:17 dpdklab
2023-10-26  7:12 dpdklab
2023-10-26  7:12 dpdklab
2023-10-26  7:11 dpdklab
2023-10-26  7:09 dpdklab
2023-10-26  7:07 dpdklab
2023-10-26  7:05 dpdklab
2023-10-26  7:02 dpdklab
2023-10-26  5:46 dpdklab
2023-10-26  5:35 dpdklab
2023-10-26  5:28 dpdklab
2023-10-26  5:21 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=653a17ec.020a0220.76143.35dbSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).