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>,
Tomasz Duszynski <tduszynski@marvell.com>
Subject: |FAILURE| pw124086-124089 [PATCH] [v11, 4/4] eal: add PMU support to tracing library
Date: Thu, 16 Feb 2023 22:57:15 +0000 (UTC) [thread overview]
Message-ID: <20230216225715.37976600AB@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2931 bytes --]
Test-Label: iol-testing
Test-Status: FAILURE
http://dpdk.org/patch/124089
_Testing issues_
Submitter: Tomasz Duszynski <tduszynski@marvell.com>
Date: Thursday, February 16 2023 17:55:02
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:01314192b7856d3737eb6d80aa351f60a07631af
124086-124089 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| RHEL 7 | FAIL |
+---------------------+----------------+
| CentOS Stream 8 | FAIL |
+---------------------+----------------+
| Debian Bullseye | FAIL |
+---------------------+----------------+
| openSUSE Leap 15 | FAIL |
+---------------------+----------------+
| Ubuntu 20.04 | FAIL |
+---------------------+----------------+
| Ubuntu 22.04 | FAIL |
+---------------------+----------------+
==== 20 line log output for Ubuntu 22.04 (dpdk_unit_test): ====
94/104 DPDK:fast-tests / telemetry_json_autotest OK 0.20 s
95/104 DPDK:fast-tests / telemetry_data_autotest OK 0.18 s
96/104 DPDK:fast-tests / table_autotest OK 15.22 s
97/104 DPDK:fast-tests / ring_pmd_autotest OK 0.18 s
98/104 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.16 s
99/104 DPDK:fast-tests / bitratestats_autotest OK 0.19 s
100/104 DPDK:fast-tests / latencystats_autotest OK 0.22 s
101/104 DPDK:fast-tests / pdump_autotest OK 5.40 s
102/104 DPDK:fast-tests / vdev_autotest OK 0.17 s
103/104 DPDK:fast-tests / compressdev_autotest SKIP 0.19 s
104/104 DPDK:fast-tests / telemetry_all SKIP 0.01 s
Ok: 94
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/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)
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)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 11.3.1-2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25429/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-16 22:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 22:57 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-16 23:11 dpdklab
2023-02-16 23:10 dpdklab
2023-02-16 23:07 dpdklab
2023-02-16 23:05 dpdklab
2023-02-16 23:01 dpdklab
2023-02-16 22:58 dpdklab
2023-02-16 22:57 dpdklab
2023-02-16 22:41 dpdklab
2023-02-16 22:16 dpdklab
2023-02-16 22:14 dpdklab
2023-02-16 22:10 dpdklab
2023-02-16 22:06 dpdklab
2023-02-16 18:37 dpdklab
2023-02-16 18:33 dpdklab
2023-02-16 18:22 dpdklab
2023-02-16 18:18 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=20230216225715.37976600AB@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=tduszynski@marvell.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).