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, David Marchand <david.marchand@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Yuying Zhang <yuying.zhang@intel.com>
Subject: |WARNING| pw106557-106558 [PATCH] [v3, 2/2] net/ice: support drop any and steer all to queue
Date: Thu, 27 Jan 2022 21:58:55 +0000 (UTC)	[thread overview]
Message-ID: <20220127215855.A5D05601B5@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-abi-testing
Test-Status: WARNING
http://dpdk.org/patch/106558

_Testing issues_

Submitter: Yuying Zhang <yuying.zhang@intel.com>
Date: Wednesday, January 26 2022 15:57:10 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:8a5a91401dc23ddab1ddea3667a17a615a25077f

106557-106558 --> testing fail

Test environment and result as below:

+-----------------------------+----------+
|         Environment         | abi_test |
+=============================+==========+
| Ubuntu 20.04 ARM GCC Native | PASS     |
+-----------------------------+----------+
| FreeBSD 13                  | FAIL     |
+-----------------------------+----------+
| Ubuntu 18.04                | PASS     |
+-----------------------------+----------+
| Ubuntu 20.04                | PASS     |
+-----------------------------+----------+

==== 20 line log output for FreeBSD 13 (abi_test): ====
^
../lib/bpf/bpf_convert.c:540:15: error: use of undeclared identifier 'ERR'
RTE_BPF_LOG(ERR, "%s: cannot get eBPF length\n", __func__);
^
../lib/bpf/bpf_convert.c:545:2: warning: implicit declaration of function 'RTE_BPF_LOG' is invalid in C99 [-Wimplicit-function-declaration]
RTE_BPF_LOG(DEBUG, "%s: prog len cBPF=%u -> eBPF=%u\n",
^
../lib/bpf/bpf_convert.c:545:14: error: use of undeclared identifier 'DEBUG'
RTE_BPF_LOG(DEBUG, "%s: prog len cBPF=%u -> eBPF=%u\n",
^
../lib/bpf/bpf_convert.c:561:15: error: use of undeclared identifier 'ERR'
RTE_BPF_LOG(ERR, "%s: cannot convert cBPF to eBPF\n", __func__);
^
6 warnings and 7 errors generated.
[241/1950] Linking target lib/librte_ethdev.so.22.1.
[242/1950] Generating symbol file 'lib/76b5a35@@rte_compressdev@sha/librte_compressdev.so.22.1.symbols'.
[243/1950] Linking target lib/librte_cmdline.so.22.1.
[244/1950] Generating symbol file 'lib/76b5a35@@rte_cryptodev@sha/librte_cryptodev.so.22.1.symbols'.
[245/1950] Compiling C object 'lib/76b5a35@@rte_efd@sta/efd_rte_efd.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====

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

FreeBSD 13
	Kernel: 13.0
	Compiler: clang 11.0.1

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

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

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

UNH-IOL DPDK Community Lab

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

                 reply	other threads:[~2022-01-27 21:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220127215855.A5D05601B5@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=yuying.zhang@intel.com \
    /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).