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, Shijith Thotton <sthotton@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw97978 [PATCH] examples/l2fwd-event: changes to use event vector
Date: Sun,  5 Sep 2021 22:19:19 -0400 (EDT)	[thread overview]
Message-ID: <20210906021919.8EDB589060@noxus.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-x86_64-compile-testing
Test-Status: WARNING
http://dpdk.org/patch/97978

_Testing issues_

Submitter: Shijith Thotton <sthotton@marvell.com>
Date: Saturday, September 04 2021 07:46:28 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:eeedef704c11bd74c367d62838700bdb8e5b573f

97978 --> testing fail

Test environment and result as below:

+---------------------+--------------------+----------------------+-------------------+
|     Environment     | dpdk_meson_compile | dpdk_mingw64_compile | dpdk_compile_spdk |
+=====================+====================+======================+===================+
| Fedora 31           | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Windows Server 2019 | PASS               | FAIL                 | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| FreeBSD 13          | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| openSUSE Leap 15    | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Fedora 32           | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Ubuntu 20.04        | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Ubuntu 18.04        | PASS               | SKIPPED              | FAIL              |
+---------------------+--------------------+----------------------+-------------------+
| CentOS 8            | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| CentOS Stream 8     | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| RHEL 7              | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Arch Linux          | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| RHEL8               | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Fedora 34           | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Fedora 33           | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Alpine              | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+
| Fedora 34 clang     | PASS               | SKIPPED              | SKIPPED           |
+---------------------+--------------------+----------------------+-------------------+

==== 20 line log output for Ubuntu 18.04 (dpdk_compile_spdk): ====
^
../examples/l2fwd-event/l2fwd_event_generic.c:260:15: error: 'struct rte_event_eth_rx_adapter_queue_conf' has no member named 'vector_mp'
eth_q_conf.vector_mp = rsrc->evt_vec_pool;
^
[2838/3118] Linking target lib/librte_vhost.so.22.0
[2839/3118] Compiling C object examples/dpdk-l2fwd-event.p/l2fwd-event_l2fwd_poll.c.o
[2840/3118] Generating symbol file drivers/librte_common_sfc_efx.so.22.0.p/librte_common_sfc_efx.so.22.0.symbols
[2841/3118] Compiling C object examples/dpdk-l2fwd-event.p/l2fwd-event_l2fwd_event.c.o
[2842/3118] Generating symbol file lib/librte_kni.so.22.0.p/librte_kni.so.22.0.symbols
[2843/3118] Generating symbol file lib/librte_eventdev.so.22.0.p/librte_eventdev.so.22.0.symbols
[2844/3118] Generating symbol file lib/librte_metrics.so.22.0.p/librte_metrics.so.22.0.symbols
[2845/3118] Generating symbol file lib/librte_gro.so.22.0.p/librte_gro.so.22.0.symbols
[2846/3118] Generating symbol file lib/librte_power.so.22.0.p/librte_power.so.22.0.symbols
[2847/3118] Generating symbol file lib/librte_efd.so.22.0.p/librte_efd.so.22.0.symbols
[2848/3118] Generating symbol file lib/librte_ip_frag.so.22.0.p/librte_ip_frag.so.22.0.symbols
[2849/3118] Generating symbol file lib/librte_gso.so.22.0.p/librte_gso.so.22.0.symbols
[2850/3118] Generating symbol file lib/librte_pdump.so.22.0.p/librte_pdump.so.22.0.symbols
[2851/3118] Generating symbol file lib/librte_lpm.so.22.0.p/librte_lpm.so.22.0.symbols
[2852/3118] Generating rte_common_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
ninja: build stopped: subcommand failed.
==== End log output ====

Fedora 31
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 9.3.1

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

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

Fedora 32
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 10.2.1

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

Ubuntu 18.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0-3ubuntu1~18.04

CentOS 8
	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 8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.4.1 20200928

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)

Arch Linux
	Kernel: 5.4.0-73-generic
	Compiler: gcc 11.1.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
	Kernel: 5.4.0-72-generic
	Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)

Fedora 33
	Kernel: 5.4.0-72-generic
	Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)

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

Fedora 34 clang
	Kernel: 5.4.0-72-generic
	Compiler: clang 12.0.0 (Fedora 12.0.0-0.3.rc1.fc34)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-09-06  2:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06  2:19 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-04  8:35 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=20210906021919.8EDB589060@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=sthotton@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).