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>,
Michael Piszczek <mpiszczek@ddn.com>
Subject: |FAILURE| pw119032 [PATCH] [v5] pci: read amd iommu virtual address width
Date: Mon, 24 Oct 2022 21:08:49 +0000 (UTC) [thread overview]
Message-ID: <20221024210849.27A1F60095@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 4044 bytes --]
Test-Label: iol-x86_64-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/119032
_Testing issues_
Submitter: Michael Piszczek <mpiszczek@ddn.com>
Date: Thursday, October 13 2022 18:16:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:269f027453ae7a9ac1bf0d6786388f598a139314
119032 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| RHEL 7 | FAIL |
+---------------------+----------------+
| Fedora 32 | FAIL |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| RHEL8 | FAIL |
+---------------------+----------------+
| Fedora 33 | FAIL |
+---------------------+----------------+
| Ubuntu 20.04 | FAIL |
+---------------------+----------------+
| Fedora 34 | FAIL |
+---------------------+----------------+
| Ubuntu 18.04 | FAIL |
+---------------------+----------------+
| Fedora 31 | FAIL |
+---------------------+----------------+
| openSUSE Leap 15 | FAIL |
+---------------------+----------------+
| Fedora 34 clang | FAIL |
+---------------------+----------------+
==== 20 line log output for Fedora 34 clang (dpdk_unit_test): ====
60/70 DPDK:fast-tests / trace_autotest_with_traces FAIL 0.02 s (exit status 255 or signal 127 SIGinvalid)
61/70 DPDK:fast-tests / metrics_autotest FAIL 0.02 s (exit status 255 or signal 127 SIGinvalid)
62/70 DPDK:fast-tests / telemetry_json_autotest FAIL 0.02 s (exit status 255 or signal 127 SIGinvalid)
63/70 DPDK:fast-tests / telemetry_data_autotest FAIL 0.02 s (exit status 255 or signal 127 SIGinvalid)
64/70 DPDK:fast-tests / table_autotest FAIL 0.02 s (exit status 255 or signal 127 SIGinvalid)
65/70 DPDK:fast-tests / ring_pmd_autotest FAIL 0.02 s (exit status 255 or signal 127 SIGinvalid)
66/70 DPDK:fast-tests / bitratestats_autotest FAIL 0.02 s (exit status 255 or signal 127 SIGinvalid)
67/70 DPDK:fast-tests / latencystats_autotest FAIL 0.02 s (exit status 255 or signal 127 SIGinvalid)
68/70 DPDK:fast-tests / pdump_autotest FAIL 0.02 s (exit status 255 or signal 127 SIGinvalid)
69/70 DPDK:fast-tests / vdev_autotest FAIL 0.02 s (exit status 255 or signal 127 SIGinvalid)
70/70 DPDK:fast-tests / telemetry_all SKIP 0.01 s
Ok: 0
Expected Fail: 0
Fail: 69
Unexpected Pass: 0
Skipped: 1
Timeout: 0
Full log written to /home-local/jenkins-local/jenkins-agent/workspace/Generic-Unit-Test-DPDK@3/dpdk/build/meson-logs/testlog.txt
==== End log output ====
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)
Fedora 32
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 10.2.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Fedora 34
Kernel: 5.4.0-72-generic
Compiler: gcc 11.1.1 20210428 (Red Hat 11.1.1-1)
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
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
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/24153/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
reply other threads:[~2022-10-24 21:08 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=20221024210849.27A1F60095@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=mpiszczek@ddn.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).