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| pw134156-134158 [PATCH] [v4,3/3] test/dma: add SG copy tes
Date: Mon, 13 Nov 2023 10:33:33 -0800 (PST)	[thread overview]
Message-ID: <65526bfd.170a0220.ed5df.8a2eSMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-compile-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/134158

_Testing issues_

Submitter: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Date: Monday, November 13 2023 12:53:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:d677a3eb1b4e2d38c193fabd755dac30ee04c2df

134156-134158 --> testing fail

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Debian Bullseye     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Buster       | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 37           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 9     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| FreeBSD 13          | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15    | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Alpine              | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| RHEL8               | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 38           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | FAIL               | FAIL                 |
+---------------------+--------------------+----------------------+

==== 20 line log output for Windows Server 2019 (dpdk_mingw64_compile): ====
^~~~
../app/test/test_dmadev.c:1251:30: error: initializer element is not constant
TEST_CASE_NAMED_WITH_DATA(param[TEST_M2D].name,
^~~~~
../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_dmadev.c:1251:30: note: (near initialization for 'ts.unit_test_cases[6].name')
TEST_CASE_NAMED_WITH_DATA(param[TEST_M2D].name,
^~~~~
../app/test/test.h:134:38: note: in definition of macro 'TEST_CASE_NAMED_WITH_DATA'
{ setup, teardown, NULL, testcase, name, 1, data }
^~~~
cc1.exe: all warnings being treated as errors
[138/733] Compiling C object app/dpdk-test.exe.p/test_test_errno.c.obj
[139/733] Compiling C object app/dpdk-test.exe.p/test_test_eal_flags.c.obj
[140/733] Linking static target lib/librte_eal.a
[141/733] Compiling C object app/dpdk-test.exe.p/test_test_hash.c.obj
[142/733] Compiling C object app/dpdk-test.exe.p/test_test_cryptodev.c.obj
ninja: build stopped: subcommand failed.
==== End log output ====

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

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

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

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

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.0

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

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

Alpine
	Kernel: 5.4.0-73-generic
	Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-13 18:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 18:33 dpdklab [this message]
2023-11-13 18:44 dpdklab
2023-11-13 21:14 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=65526bfd.170a0220.ed5df.8a2eSMTPIN_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).