From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
"David Marchand" <david.marchand@redhat.com>,
"Thomas Monjalon" <thomas@monjalon.net>,
"Morten Brørup" <mb@smartsharesystems.com>
Subject: |FAILURE| pw117504 [PATCH] eal: non-temporal memcpy
Date: Thu, 6 Oct 2022 21:43:55 +0000 (UTC) [thread overview]
Message-ID: <20221006214355.8E49D601BB@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 4636 bytes --]
Test-Label: iol-x86_64-compile-testing
Test-Status: FAILURE
http://dpdk.org/patch/117504
_Testing issues_
Submitter: Morten Brørup <mb@smartsharesystems.com>
Date: Thursday, October 06 2022 20:34:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4ed890495594a71e618d62fd975c5868915eb4a1
117504 --> testing fail
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2019 | FAIL | PASS |
+---------------------+--------------------+----------------------+
| RHEL 7 | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
| FreeBSD 13 | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 31 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 34 clang | FAIL | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 18.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 34 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 32 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 33 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
==== 20 line log output for Fedora 34 clang (dpdk_meson_compile): ====
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/eal/include/rte_common.h:417:56: note: expanded from macro 'RTE_BUILD_BUG_ON'
#define RTE_BUILD_BUG_ON(condition) ((void)sizeof(char[1 - 2*!!(condition)]))
^~~~~~~~~~~~~~~~~~~
In file included from ../lib/eal/common/eal_common_options.c:32:
../lib/eal/x86/include/rte_memcpy.h:1965:2: error: array size is negative
RTE_BUILD_BUG_ON(!__builtin_constant_p(flags));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/eal/include/rte_common.h:417:56: note: expanded from macro 'RTE_BUILD_BUG_ON'
#define RTE_BUILD_BUG_ON(condition) ((void)sizeof(char[1 - 2*!!(condition)]))
^~~~~~~~~~~~~~~~~~~
In file included from ../lib/eal/common/eal_common_options.c:32:
../lib/eal/x86/include/rte_memcpy.h:1987:2: error: array size is negative
RTE_BUILD_BUG_ON(!__builtin_constant_p(flags));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/eal/include/rte_common.h:417:56: note: expanded from macro 'RTE_BUILD_BUG_ON'
#define RTE_BUILD_BUG_ON(condition) ((void)sizeof(char[1 - 2*!!(condition)]))
^~~~~~~~~~~~~~~~~~~
13 errors generated.
ninja: build stopped: subcommand failed.
==== End log output ====
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
Fedora 31
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
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 34 clang
Kernel: 5.4.0-72-generic
Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)
Ubuntu 18.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0-3ubuntu1~18.04
Fedora 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Fedora 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
Fedora 33
Kernel: 5.4.0-72-generic
Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/23814/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-10-06 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 21:43 dpdklab [this message]
[not found] <20221006203426.78743-1-mb@smartsharesystems.com>
2022-10-06 21:39 ` 0-day Robot
-- strict thread matches above, loose matches on Subject: below --
2022-10-06 21:36 dpdklab
2022-10-06 21:26 dpdklab
2022-10-06 20:59 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=20221006214355.8E49D601BB@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=mb@smartsharesystems.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).