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,
	David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Ankur Dwivedi <adwivedi@marvell.com>
Subject: |FAILURE| pw121905-121910 [PATCH] [v5, 6/6] ethdev: add trace points for tm
Date: Thu, 12 Jan 2023 21:19:08 +0000 (UTC)	[thread overview]
Message-ID: <20230112211908.519FB60092@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 5485 bytes --]

Test-Label: iol-testing
Test-Status: FAILURE
http://dpdk.org/patch/121910

_Testing issues_

Submitter: Ankur Dwivedi <adwivedi@marvell.com>
Date: Thursday, January 12 2023 11:21:40 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:7f6b150cb79dad10b82fe004e5b2310e39507381

121905-121910 --> testing fail

Test environment and result as below:

+-------------------------------+----------------+--------------------+----------------------+
|          Environment          | dpdk_unit_test | dpdk_meson_compile | dpdk_mingw64_compile |
+===============================+================+====================+======================+
| Ubuntu 20.04 ARM GCC Native   | PASS           | PASS               | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| Ubuntu 20.04 ARM Clang Native | PASS           | PASS               | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| Windows Server 2019           | FAIL           | FAIL               | FAIL                 |
+-------------------------------+----------------+--------------------+----------------------+
| CentOS Stream 8               | PASS           | PASS               | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| Ubuntu 20.04                  | PASS           | PASS               | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| Ubuntu 22.04                  | PASS           | PASS               | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| RHEL 7                        | PASS           | PASS               | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| Debian Bullseye               | PASS           | PASS               | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| RHEL8                         | PASS           | PASS               | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| CentOS Stream 9               | PASS           | PASS               | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| Debian Buster                 | PASS           | PASS               | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| FreeBSD 13                    | SKIPPED        | PASS               | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+
| openSUSE Leap 15              | SKIPPED        | PASS               | SKIPPED              |
+-------------------------------+----------------+--------------------+----------------------+

==== 20 line log output for Windows Server 2019 (dpdk_mingw64_compile): ====
__VA_ARGS__ \
^~~~~~~~~~~
..\lib\ethdev/rte_ethdev_trace_fp.h:510:1: note: in expansion of macro 'RTE_TRACE_POINT_FP'
RTE_TRACE_POINT_FP(
^~~~~~~~~~~~~~~~~~
..\lib\eal\include/rte_trace_point_register.h:38:2: note: in expansion of macro 'RTE_BUILD_BUG_ON'
RTE_BUILD_BUG_ON(sizeof(type) != sizeof(typeof(in))); \
^~~~~~~~~~~~~~~~
..\lib\eal\include/rte_trace_point.h:404:38: note: in expansion of macro '__rte_trace_point_emit'
#define rte_trace_point_emit_u64(in) __rte_trace_point_emit(in, uint64_t)
^~~~~~~~~~~~~~~~~~~~~~
..\lib\ethdev/rte_ethdev_trace_fp.h:516:2: note: in expansion of macro 'rte_trace_point_emit_u64'
rte_trace_point_emit_u64(time->tv_nsec);
^~~~~~~~~~~~~~~~~~~~~~~~
[247/669] Compiling C object lib/librte_rcu.a.p/rcu_rte_rcu_qsbr.c.obj
[248/669] Linking target lib/librte_pci-23.dll
[249/669] Linking target lib/librte_timer-23.dll
[250/669] Compiling C object lib/librte_ethdev.a.p/ethdev_rte_class_eth.c.obj
[251/669] Linking target lib/librte_cfgfile-23.dll
ninja: build stopped: subcommand failed.
==== End log output ====

Ubuntu 20.04 ARM GCC Native
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

Ubuntu 20.04 ARM Clang Native
	Kernel: 5.4.0-53-generic
	Compiler: clang 10.0.0-4ubuntu1

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

Ubuntu 20.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.0-17ubuntu1~20.04

Ubuntu 22.04
	Kernel: Container Host Kernel
	Compiler: gcc 12.2.1-2

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)

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

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

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

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-01-12 21:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 21:19 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-12 23:17 dpdklab
2023-01-12 21:20 dpdklab
2023-01-12 21:19 dpdklab
2023-01-12 21:19 dpdklab
2023-01-12 21:18 dpdklab
2023-01-12 21:18 dpdklab
2023-01-12 21:18 dpdklab
2023-01-12 21:17 dpdklab
2023-01-12 21:17 dpdklab
2023-01-12 21:17 dpdklab
     [not found] <20230112112140.807233-7-adwivedi@marvell.com>
2023-01-12 11:22 ` |FAILURE| pw121905-121910 [PATCH v5 " qemudev
2023-01-12 12:42 ` qemudev
2023-01-12 12:24 |FAILURE| pw121905-121910 [PATCH] [v5, " dpdklab
2023-01-12 12:16 dpdklab
2023-01-12 12:05 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=20230112211908.519FB60092@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=adwivedi@marvell.com \
    --cc=david.marchand@redhat.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).