automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, Yanling Song <songyl@ramaxel.com>
Subject: |FAILURE| pw105239-105264 [PATCH] [v1, 25/25] net/spnic: add doc infrastructure
Date: Sat, 18 Dec 2021 03:21:13 +0000 (UTC)	[thread overview]
Message-ID: <20211218032113.D857E6025C@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-x86_64-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/105264

_Testing issues_

Submitter: Yanling Song <songyl@ramaxel.com>
Date: Saturday, December 18 2021 02:51:52 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:042f5a355a57b31a9f87824173a9d427b21abdb8

105239-105264 --> testing fail

Test environment and result as below:

+------------------+----------------+
|   Environment    | dpdk_unit_test |
+==================+================+
| Arch Linux       | FAIL           |
+------------------+----------------+
| Ubuntu 18.04     | FAIL           |
+------------------+----------------+
| Fedora 31        | FAIL           |
+------------------+----------------+
| CentOS Stream 8  | FAIL           |
+------------------+----------------+
| openSUSE Leap 15 | FAIL           |
+------------------+----------------+
| CentOS 8         | FAIL           |
+------------------+----------------+
| RHEL 7           | FAIL           |
+------------------+----------------+
| Ubuntu 20.04     | FAIL           |
+------------------+----------------+
| RHEL8            | FAIL           |
+------------------+----------------+
| Fedora 34        | FAIL           |
+------------------+----------------+
| Fedora 33        | FAIL           |
+------------------+----------------+
| Fedora 34 clang  | FAIL           |
+------------------+----------------+
| Fedora 32        | FAIL           |
+------------------+----------------+

==== 20 line log output for Fedora 32 (dpdk_unit_test): ====
|                                              ~~~~~~^~~~~~~~~~
cc1: all warnings being treated as errors
[1993/2904] Compiling C object 'drivers/a715181@@tmp_rte_net_tap@sta/net_tap_rte_eth_tap.c.o'.
[1994/2904] Compiling C object 'drivers/net/thunderx/base/80ab7c6@@nicvf_base@sta/nicvf_hw.c.o'.
[1995/2904] Compiling C object 'drivers/a715181@@tmp_rte_net_thunderx@sta/net_thunderx_nicvf_svf.c.o'.
[1996/2904] Compiling C object 'drivers/net/thunderx/base/80ab7c6@@nicvf_base@sta/nicvf_mbox.c.o'.
[1997/2904] Compiling C object 'drivers/net/txgbe/base/441365e@@txgbe_base@sta/txgbe_hw.c.o'.
[1998/2904] Generating rte_net_sfc.pmd.c with a custom command.
[1999/2904] Generating rte_net_softnic.pmd.c with a custom command.
[2000/2904] Compiling C object 'drivers/a715181@@tmp_rte_net_spnic@sta/net_spnic_spnic_io.c.o'.
[2001/2904] Compiling C object 'drivers/net/spnic/base/448fc72@@spnic_base@sta/spnic_hw_comm.c.o'.
[2002/2904] Compiling C object 'drivers/net/thunderx/base/80ab7c6@@nicvf_base@sta/nicvf_bsvf.c.o'.
[2003/2904] Compiling C object 'drivers/a715181@@tmp_rte_net_thunderx@sta/net_thunderx_nicvf_rxtx.c.o'.
[2004/2904] Compiling C object 'drivers/a715181@@tmp_rte_net_thunderx@sta/net_thunderx_nicvf_ethdev.c.o'.
[2005/2904] Compiling C object 'drivers/net/spnic/base/448fc72@@spnic_base@sta/spnic_nic_cfg.c.o'.
[2006/2904] Compiling C object 'drivers/net/spnic/base/448fc72@@spnic_base@sta/spnic_mbox.c.o'.
[2007/2904] Compiling C object 'drivers/a715181@@tmp_rte_net_spnic@sta/net_spnic_spnic_rx.c.o'.
[2008/2904] Compiling C object 'drivers/a715181@@tmp_rte_net_spnic@sta/net_spnic_spnic_tx.c.o'.
[2009/2904] Compiling C object 'drivers/a715181@@tmp_rte_net_spnic@sta/net_spnic_spnic_ethdev.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====

Arch Linux
	Kernel: 5.4.0-73-generic
	Compiler: gcc 11.1.0

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

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

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

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

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)

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)

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

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)

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

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

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-12-18  3:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-18  3:21 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-12-18  3:35 dpdklab
2021-12-18  3:33 dpdklab
2021-12-18  3:32 dpdklab
2021-12-18  3:20 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=20211218032113.D857E6025C@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=songyl@ramaxel.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).