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, Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-test-report] |FAILURE| pw100000 [PATCH] [v3] telemetry: fix "in-memory" process socket conflicts
Date: Mon,  4 Oct 2021 14:18:03 -0400 (EDT)	[thread overview]
Message-ID: <20211004181803.59F7B6D535@noxus.dpdklab.iol.unh.edu> (raw)

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

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

_Testing issues_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Wednesday, September 29 2021 13:54:38 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:086d426406bd3f6fac96a15bbd871c7fe714bc2d

100000 --> testing fail

Test environment and result as below:

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

==== 20 line log output for Fedora 34 clang (dpdk_unit_test): ====
15/94 DPDK:fast-tests / eal_flags_a_opt_autotest       FAIL           0.37s (exit status 255 or signal 127 SIGinvalid)
16/94 DPDK:fast-tests / eal_flags_b_opt_autotest       FAIL           0.55s (exit status 255 or signal 127 SIGinvalid)
18/94 DPDK:fast-tests / eal_flags_r_opt_autotest       FAIL           0.66s (exit status 255 or signal 127 SIGinvalid)
19/94 DPDK:fast-tests / eal_flags_mem_autotest         FAIL           0.48s (exit status 255 or signal 127 SIGinvalid)
20/94 DPDK:fast-tests / eal_flags_file_prefix_autotest FAIL           4.45s (exit status 255 or signal 127 SIGinvalid)
21/94 DPDK:fast-tests / eal_flags_misc_autotest        FAIL           0.27s (exit status 255 or signal 127 SIGinvalid)
75/94 DPDK:fast-tests / ipsec_autotest                 SKIP           0.17s
76/94 DPDK:fast-tests / kni_autotest                   SKIP           0.17s
80/94 DPDK:fast-tests / power_cpufreq_autotest         SKIP           0.17s
82/94 DPDK:fast-tests / power_kvm_vm_autotest          SKIP           0.18s
94/94 DPDK:fast-tests / compressdev_autotest           SKIP           0.17s

Ok:                 79
Expected Fail:      0
Fail:               10
Unexpected Pass:    0
Skipped:            5
Timeout:            0

Full log written to /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK/dpdk/build/meson-logs/testlog.txt
==== End log output ====

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)

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

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)

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)

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

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

Fedora 32
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 10.2.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

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)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2021-10-04 18:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 18:18 dpdklab [this message]
2021-10-04 19:37 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=20211004181803.59F7B6D535@noxus.dpdklab.iol.unh.edu \
    --to=dpdklab@iol.unh.edu \
    --cc=bruce.richardson@intel.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).