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>,
	Tomasz Duszynski <tduszynski@marvell.com>
Subject: |FAILURE| pw123785-123788 [PATCH] [v10, 4/4] eal: add PMU support to tracing library
Date: Mon, 13 Feb 2023 18:09:41 +0000 (UTC)	[thread overview]
Message-ID: <20230213180941.5DE516009A@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)

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

Test-Label: iol-testing
Test-Status: FAILURE
http://dpdk.org/patch/123788

_Testing issues_

Submitter: Tomasz Duszynski <tduszynski@marvell.com>
Date: Monday, February 13 2023 11:31:56 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:39d469a7eb4f157923be73aea0b0cc1015860ca7

123785-123788 --> testing fail

Test environment and result as below:

+------------------------------------+----------------+--------------------+
|            Environment             | dpdk_unit_test | dpdk_meson_compile |
+====================================+================+====================+
| Ubuntu 20.04 ARM GCC Native        | FAIL           | PASS               |
+------------------------------------+----------------+--------------------+
| Ubuntu 20.04 ARM Clang Native      | FAIL           | PASS               |
+------------------------------------+----------------+--------------------+
| Windows Server 2019                | PASS           | SKIPPED            |
+------------------------------------+----------------+--------------------+
| Ubuntu 22.04                       | FAIL           | SKIPPED            |
+------------------------------------+----------------+--------------------+
| RHEL 7                             | FAIL           | SKIPPED            |
+------------------------------------+----------------+--------------------+
| openSUSE Leap 15                   | FAIL           | SKIPPED            |
+------------------------------------+----------------+--------------------+
| CentOS Stream 9                    | FAIL           | SKIPPED            |
+------------------------------------+----------------+--------------------+
| CentOS Stream 8                    | FAIL           | SKIPPED            |
+------------------------------------+----------------+--------------------+
| Debian Bullseye                    | FAIL           | SKIPPED            |
+------------------------------------+----------------+--------------------+
| RHEL8                              | FAIL           | SKIPPED            |
+------------------------------------+----------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | SKIPPED        | PASS               |
+------------------------------------+----------------+--------------------+
| Ubuntu 20.04 ARM SVE               | SKIPPED        | PASS               |
+------------------------------------+----------------+--------------------+

==== 20 line log output for RHEL8 (dpdk_unit_test): ====
94/104 DPDK:fast-tests / telemetry_json_autotest  OK       0.26 s
95/104 DPDK:fast-tests / telemetry_data_autotest  OK       0.17 s
96/104 DPDK:fast-tests / table_autotest        OK       8.36 s
97/104 DPDK:fast-tests / ring_pmd_autotest     OK       0.20 s
98/104 DPDK:fast-tests / event_eth_tx_adapter_autotest  OK       0.56 s
99/104 DPDK:fast-tests / bitratestats_autotest  OK       0.17 s
100/104 DPDK:fast-tests / latencystats_autotest  OK       0.28 s
101/104 DPDK:fast-tests / pdump_autotest        OK       5.21 s
102/104 DPDK:fast-tests / vdev_autotest         OK       0.17 s
103/104 DPDK:fast-tests / compressdev_autotest  SKIP     0.23 s
104/104 DPDK:fast-tests / telemetry_all         SKIP     0.03 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@2/dpdk/build/meson-logs/testlog.txt
==== End log output ====

Ubuntu 20.04 ARM GCC Native
	Kernel: 5.4.0-53-generic
	Compiler: gcc 9.3

Ubuntu 20.04 ARM Clang Native
	Kernel: 5.4.0-53-generic
	Compiler: clang 10.0.0-4ubuntu1

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

Ubuntu 22.04
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.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)

openSUSE Leap 15
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 7.5.0

CentOS Stream 9
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 11.3.1 20220421

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

RHEL8
	Kernel: 4.18.0-240.10.1.el8_3.x86_64
	Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)

Ubuntu 20.04 ARM GCC Cross Compile
	Kernel: 5.4.0-72-generic
	Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0

Ubuntu 20.04 ARM SVE
	Kernel: 5.4.0-80-generic
	Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)

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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-02-13 18:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 18:09 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-02-13 18:12 dpdklab
2023-02-13 18:12 dpdklab
2023-02-13 18:10 dpdklab
2023-02-13 18:04 dpdklab
2023-02-13 17:56 dpdklab
2023-02-13 17:54 dpdklab
2023-02-13 17:52 dpdklab
2023-02-13 17:51 dpdklab
2023-02-13 17:49 dpdklab
2023-02-13 17:45 dpdklab
2023-02-13 17:42 dpdklab
2023-02-13 17:40 dpdklab
2023-02-13 12:57 dpdklab
2023-02-13 12:02 dpdklab
2023-02-13 12:02 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=20230213180941.5DE516009A@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).