automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |FAILURE| [GIT MASTER] 655eb37b18b1b0dc4d106acdf0dfedde01cfb224
Date: Wed, 12 Jul 2023 14:48:35 -0700 (PDT)	[thread overview]
Message-ID: <64af1fb3.050a0220.7f4d9.f689SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: dpdk

655eb37b18b1b0dc4d106acdf0dfedde01cfb224 --> testing fail

Test environment and result as below:

+--------------------------+----------------+
|       Environment        | dpdk_unit_test |
+==========================+================+
| Fedora 37 (ARM)          | FAIL           |
+--------------------------+----------------+
| Fedora 38 (ARM)          | FAIL           |
+--------------------------+----------------+
| CentOS Stream 9 (ARM)    | FAIL           |
+--------------------------+----------------+
| Ubuntu 20.04 (ARM)       | PASS           |
+--------------------------+----------------+
| Fedora 38 (ARM Clang)    | FAIL           |
+--------------------------+----------------+
| Debian Bullseye          | PASS           |
+--------------------------+----------------+
| Fedora 38                | FAIL           |
+--------------------------+----------------+
| CentOS Stream 9          | FAIL           |
+--------------------------+----------------+
| Debian 11 (Buster) (ARM) | PASS           |
+--------------------------+----------------+
| Fedora 37                | FAIL           |
+--------------------------+----------------+
| Debian Buster            | PASS           |
+--------------------------+----------------+
| Ubuntu 22.04             | PASS           |
+--------------------------+----------------+
| openSUSE Leap 15         | FAIL           |
+--------------------------+----------------+
| RHEL 7                   | FAIL           |
+--------------------------+----------------+
| Arch Linux               | PASS           |
+--------------------------+----------------+
| RHEL8                    | FAIL           |
+--------------------------+----------------+
| Ubuntu 20.04             | PASS           |
+--------------------------+----------------+
| CentOS Stream 8          | FAIL           |
+--------------------------+----------------+

==== 20 line log output for CentOS Stream 8 (dpdk_unit_test): ====
97/107 DPDK:fast-tests / table_autotest        OK      17.12 s
98/107 DPDK:fast-tests / ring_pmd_autotest     OK       0.17 s
99/107 DPDK:fast-tests / event_eth_tx_adapter_autotest  OK       1.36 s
100/107 DPDK:fast-tests / bitratestats_autotest  OK       0.46 s
101/107 DPDK:fast-tests / latencystats_autotest  OK       0.46 s
102/107 DPDK:fast-tests / pdump_autotest        OK       5.67 s
103/107 DPDK:fast-tests / vdev_autotest         OK       0.39 s
104/107 DPDK:fast-tests / rawdev_autotest       OK       0.17 s
105/107 DPDK:fast-tests / pdcp_autotest         SKIP     0.43 s
106/107 DPDK:fast-tests / compressdev_autotest  SKIP     0.35 s
107/107 DPDK:fast-tests / telemetry_all         SKIP     0.01 s

Ok:                   96
Expected Fail:         0
Fail:                  1
Unexpected Pass:       0
Skipped:              10
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 ====

Fedora 37 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 12.3.1

Fedora 38 (ARM)
	Kernel: Depends on container host
	Compiler: gcc 13.1.1

CentOS Stream 9 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 11.3.1

Ubuntu 20.04 (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 9.4.0

Fedora 38 (ARM Clang)
	Kernel: Depends on container host
	Compiler: clang 16.0.3

Debian Bullseye
	Kernel: 5.4.0-122-generic
	Compiler: gcc 10.2.1-6

Fedora 38
	Kernel: Depends on container host
	Compiler: clang 16.0.3

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

Debian 11 (Buster) (ARM)
	Kernel: Container Host Kernel
	Compiler: gcc 10.2.1

Fedora 37
	Kernel: Depends on container host system
	Compiler: gcc 12.3.1

Debian Buster
	Kernel: 5.4.0-122-generic
	Compiler: gcc 8.3.0-6

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

Arch Linux
	Kernel: 5.4.0-73-generic
	Compiler: gcc 11.1.0

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
	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/tarballs/25473/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-07-12 21:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12 21:48 dpdklab [this message]
2023-07-13  2:12 dpdklab
2023-07-13 17:31 dpdklab
2023-07-13 21:08 dpdklab
2023-07-14  2:38 dpdklab
2023-07-15  2:04 dpdklab
2023-07-16  2:05 dpdklab
2023-07-17  2:03 dpdklab
2023-07-18  1:57 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=64af1fb3.050a0220.7f4d9.f689SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).