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,
	Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Subject: |FAILURE| pw137801-137807 [PATCH] [RFC,7/7] eal: deprecate relaxed f
Date: Sat, 02 Mar 2024 11:21:23 -0800 (PST)	[thread overview]
Message-ID: <65e37c33.020a0220.f4e31.a638SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240302135328.531940-8-mattias.ronnblom@ericsson.com>

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

_Testing issues_

Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Saturday, March 02 2024 13:53:28 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:5df34de5808a7b826b8bc035d6ee3161a12be364

137801-137807 --> testing fail

Test environment and result as below:

+---------------------+--------------------+----------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| Windows Server 2022 | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| FreeBSD 13.2        | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | FAIL               | PASS                 |
+---------------------+--------------------+----------------------+
| CentOS Stream 8     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 37           | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Fedora 38           | FAIL               | SKIPPED              |
+---------------------+--------------------+----------------------+
| CentOS Stream 9     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian Bullseye     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Debian 12 (arm)     | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15    | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04        | PASS               | SKIPPED              |
+---------------------+--------------------+----------------------+

==== 20 line log output for Fedora 38 (dpdk_meson_compile): ====
__RTE_GEN_BIT_ATOMIC_OPS(64)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/eal/include/rte_bitops.h:1166:2: note: expanded from macro '__RTE_GEN_BIT_ATOMIC_OPS'
__RTE_GEN_BIT_ATOMIC_TEST_AND_ASSIGN(size)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../lib/eal/include/rte_bitops.h:1151:55: note: expanded from macro '__RTE_GEN_BIT_ATOMIC_TEST_AND_ASSIGN'
} while(!__atomic_compare_exchange_n(addr, &before, after, \
^~~~~
../lib/eal/include/rte_bitops.h:1169:1: note: variable 'after' is declared here
../lib/eal/include/rte_bitops.h:1166:2: note: expanded from macro '__RTE_GEN_BIT_ATOMIC_OPS'
__RTE_GEN_BIT_ATOMIC_TEST_AND_ASSIGN(size)
^
../lib/eal/include/rte_bitops.h:1145:3: note: expanded from macro '__RTE_GEN_BIT_ATOMIC_TEST_AND_ASSIGN'
uint ## size ## _t after;                               \
^
<scratch space>:260:1: note: expanded from here
uint64_t
^
2 errors generated.
ninja: build stopped: subcommand failed.
==== End log output ====

Windows Server 2022
	Kernel: OS Build 20348.2031
	Compiler: MSVC VS-Preview

FreeBSD 13.2
	Kernel: 13.2
	Compiler: clang 11.3.0

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

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

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

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

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

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

Debian 12 (arm)
	Kernel: Container Host Kernel
	Compiler: gcc 11

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/29385/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-02 19:21 UTC|newest]

Thread overview: 97+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240302135328.531940-8-mattias.ronnblom@ericsson.com>
2024-03-02 13:40 ` |SUCCESS| pw137801-137807 [RFC 7/7] eal: deprecate relaxed family of bit operations qemudev
2024-03-02 13:45 ` qemudev
2024-03-02 14:05 ` |SUCCESS| pw137807 " checkpatch
2024-03-02 15:05 ` |FAILURE| " 0-day Robot
2024-03-02 18:47 ` |FAILURE| pw137801-137807 [PATCH] [RFC,7/7] eal: deprecate relaxed f dpdklab
2024-03-02 18:48 ` |SUCCESS| " dpdklab
2024-03-02 18:49 ` |FAILURE| " dpdklab
2024-03-02 18:49 ` dpdklab
2024-03-02 18:56 ` dpdklab
2024-03-02 18:56 ` dpdklab
2024-03-02 18:56 ` |SUCCESS| " dpdklab
2024-03-02 18:57 ` dpdklab
2024-03-02 18:57 ` dpdklab
2024-03-02 18:59 ` |FAILURE| " dpdklab
2024-03-02 19:00 ` dpdklab
2024-03-02 19:00 ` dpdklab
2024-03-02 19:00 ` dpdklab
2024-03-02 19:01 ` |SUCCESS| " dpdklab
2024-03-02 19:01 ` dpdklab
2024-03-02 19:01 ` |FAILURE| " dpdklab
2024-03-02 19:02 ` |SUCCESS| " dpdklab
2024-03-02 19:03 ` dpdklab
2024-03-02 19:04 ` dpdklab
2024-03-02 19:05 ` dpdklab
2024-03-02 19:11 ` dpdklab
2024-03-02 19:14 ` |FAILURE| " dpdklab
2024-03-02 19:15 ` dpdklab
2024-03-02 19:15 ` dpdklab
2024-03-02 19:15 ` |SUCCESS| " dpdklab
2024-03-02 19:15 ` |FAILURE| " dpdklab
2024-03-02 19:16 ` dpdklab
2024-03-02 19:16 ` |SUCCESS| " dpdklab
2024-03-02 19:17 ` dpdklab
2024-03-02 19:17 ` dpdklab
2024-03-02 19:17 ` dpdklab
2024-03-02 19:18 ` |FAILURE| " dpdklab
2024-03-02 19:18 ` |SUCCESS| " dpdklab
2024-03-02 19:18 ` dpdklab
2024-03-02 19:18 ` |FAILURE| " dpdklab
2024-03-02 19:18 ` |SUCCESS| " dpdklab
2024-03-02 19:18 ` |FAILURE| " dpdklab
2024-03-02 19:19 ` dpdklab
2024-03-02 19:19 ` dpdklab
2024-03-02 19:19 ` dpdklab
2024-03-02 19:19 ` |SUCCESS| " dpdklab
2024-03-02 19:20 ` dpdklab
2024-03-02 19:20 ` |FAILURE| " dpdklab
2024-03-02 19:20 ` dpdklab
2024-03-02 19:21 ` dpdklab
2024-03-02 19:21 ` dpdklab [this message]
2024-03-02 19:22 ` dpdklab
2024-03-02 19:22 ` dpdklab
2024-03-02 19:22 ` dpdklab
2024-03-02 19:24 ` dpdklab
2024-03-02 19:24 ` dpdklab
2024-03-02 19:25 ` dpdklab
2024-03-02 19:29 ` dpdklab
2024-03-02 19:32 ` dpdklab
2024-03-02 19:37 ` dpdklab
2024-03-02 19:42 ` dpdklab
2024-03-02 19:46 ` dpdklab
2024-03-02 19:47 ` dpdklab
2024-03-02 19:48 ` dpdklab
2024-03-02 19:58 ` dpdklab
2024-03-02 20:01 ` dpdklab
2024-03-02 20:44 ` dpdklab
2024-03-02 20:54 ` dpdklab
2024-03-02 20:57 ` dpdklab
2024-03-02 21:00 ` dpdklab
2024-03-02 21:16 ` |SUCCESS| " dpdklab
2024-03-02 21:24 ` dpdklab
2024-03-02 22:35 ` |FAILURE| " dpdklab
2024-03-02 22:37 ` dpdklab
2024-03-02 23:01 ` dpdklab
2024-03-03  4:41 ` |SUCCESS| " dpdklab
2024-03-06 13:09 ` dpdklab
2024-03-06 13:36 ` dpdklab
2024-03-06 14:05 ` dpdklab
2024-04-26 22:21 ` |FAILURE| " dpdklab
2024-04-26 22:25 ` dpdklab
2024-04-26 22:26 ` dpdklab
2024-04-26 22:29 ` dpdklab
2024-04-26 22:29 ` dpdklab
2024-04-26 22:30 ` dpdklab
2024-04-26 22:32 ` dpdklab
2024-04-26 22:36 ` dpdklab
2024-04-26 22:42 ` dpdklab
2024-04-26 22:42 ` dpdklab
2024-04-26 22:43 ` dpdklab
2024-04-26 22:46 ` dpdklab
2024-04-26 22:47 ` dpdklab
2024-04-26 22:47 ` dpdklab
2024-04-26 22:48 ` dpdklab
2024-04-26 22:49 ` dpdklab
2024-04-26 22:51 ` dpdklab
2024-04-26 23:16 ` dpdklab
2024-04-26 23:26 ` 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=65e37c33.020a0220.f4e31.a638SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=mattias.ronnblom@ericsson.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).