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>,
	Weiguo Li <liwg06@foxmail.com>
Subject: |FAILURE| pw106764 [PATCH] eventdev/eth_rx: fix memory leak when token parsing finished
Date: Wed,  2 Feb 2022 08:36:25 +0000 (UTC)	[thread overview]
Message-ID: <20220202083625.9162D601B5@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

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

_Testing issues_

Submitter: Weiguo Li <liwg06@foxmail.com>
Date: Wednesday, February 02 2022 06:15:41 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:60e68d170b122d86c1c49cc51078db461542a26b

106764 --> testing fail

Test environment and result as below:

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

==== 20 line log output for Fedora 34 clang (dpdk_unit_test): ====
^
6 errors generated.
[270/3324] Generating symbol file 'lib/76b5a35@@rte_metrics@sha/librte_metrics.so.22.1.symbols'.
[271/3324] Generating symbol file 'lib/76b5a35@@rte_bpf@sha/librte_bpf.so.22.1.symbols'.
[272/3324] Compiling C object 'lib/76b5a35@@rte_efd@sta/efd_rte_efd.c.o'.
[273/3324] Compiling C object 'lib/76b5a35@@rte_cryptodev@sta/cryptodev_rte_cryptodev.c.o'.
[274/3324] Compiling C object 'lib/76b5a35@@rte_eventdev@sta/eventdev_rte_event_crypto_adapter.c.o'.
[275/3324] Compiling C object 'lib/76b5a35@@rte_gro@sta/gro_gro_tcp4.c.o'.
[276/3324] Compiling C object 'lib/76b5a35@@rte_gro@sta/gro_rte_gro.c.o'.
[277/3324] Compiling C object 'lib/76b5a35@@rte_gro@sta/gro_gro_udp4.c.o'.
[278/3324] Compiling C object 'lib/76b5a35@@rte_gso@sta/gso_gso_tcp4.c.o'.
[279/3324] Compiling C object 'lib/76b5a35@@rte_gpudev@sta/gpudev_gpudev.c.o'.
[280/3324] Compiling C object 'lib/76b5a35@@rte_gro@sta/gro_gro_vxlan_tcp4.c.o'.
[281/3324] Compiling C object 'lib/76b5a35@@rte_eventdev@sta/eventdev_rte_event_timer_adapter.c.o'.
[282/3324] Compiling C object 'lib/76b5a35@@rte_gso@sta/gso_gso_udp4.c.o'.
[283/3324] Compiling C object 'lib/76b5a35@@rte_gso@sta/gso_gso_common.c.o'.
[284/3324] Compiling C object 'lib/76b5a35@@rte_eventdev@sta/eventdev_rte_event_eth_tx_adapter.c.o'.
[285/3324] Compiling C object 'lib/76b5a35@@rte_gro@sta/gro_gro_vxlan_udp4.c.o'.
[286/3324] Compiling C object 'lib/76b5a35@@rte_eventdev@sta/eventdev_rte_eventdev.c.o'.
ninja: build stopped: subcommand failed.
==== End log output ====

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

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

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)

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 33
	Kernel: 5.4.0-72-generic
	Compiler: gcc 10.3.1 20210422 (Red Hat 10.3.1-1)

Fedora 34
	Kernel: 5.4.0-72-generic
	Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)

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

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

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

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

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

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)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2022-02-02  8:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02  8:36 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-02-02  9:23 dpdklab
2022-02-02  8:30 dpdklab
     [not found] <tencent_7F6E319F3CF5A71211493A97DF15231B2208@qq.com>
2022-02-02  7:59 ` 0-day Robot

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=20220202083625.9162D601B5@dpdk-ubuntu.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=david.marchand@redhat.com \
    --cc=liwg06@foxmail.com \
    --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).