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>,
"Hunt, David" <david.hunt@intel.com>
Subject: |FAILURE| pw121071-121073 [PATCH] [v1, 3/3] doc/power: remove empty poll documentation
Date: Tue, 20 Dec 2022 15:01:36 +0000 (UTC) [thread overview]
Message-ID: <20221220150136.38B1A6008E@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3472 bytes --]
Test-Label: iol-x86_64-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/121073
_Testing issues_
Submitter: Hunt, David <david.hunt@intel.com>
Date: Tuesday, December 20 2022 12:56:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c581c49cd3fcaff596fbe566e270b442e6326c79
121071-121073 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| RHEL8 | PASS |
+---------------------+----------------+
| RHEL 7 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian Buster | FAIL |
+---------------------+----------------+
| Ubuntu 20.04 | FAIL |
+---------------------+----------------+
| CentOS Stream 8 | FAIL |
+---------------------+----------------+
==== 20 line log output for CentOS Stream 8 (dpdk_unit_test): ====
93/103 DPDK:fast-tests / telemetry_json_autotest OK 0.17 s
94/103 DPDK:fast-tests / telemetry_data_autotest OK 0.25 s
95/103 DPDK:fast-tests / table_autotest FAIL 1.36 s (exit status 255 or signal 127 SIGinvalid)
96/103 DPDK:fast-tests / ring_pmd_autotest OK 0.17 s
97/103 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 0.89 s
98/103 DPDK:fast-tests / bitratestats_autotest OK 0.27 s
99/103 DPDK:fast-tests / latencystats_autotest OK 0.17 s
100/103 DPDK:fast-tests / pdump_autotest OK 5.36 s
101/103 DPDK:fast-tests / vdev_autotest OK 0.90 s
102/103 DPDK:fast-tests / compressdev_autotest SKIP 0.48 s
103/103 DPDK:fast-tests / telemetry_all SKIP 0.01 s
Ok: 93
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 9
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 ====
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 12.2.1-2
RHEL8
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)
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/24782/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-12-20 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 15:01 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-20 15:01 dpdklab
2022-12-20 15:00 dpdklab
2022-12-20 15:00 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=20221220150136.38B1A6008E@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.hunt@intel.com \
--cc=david.marchand@redhat.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).