From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Ophir Munk <ophirmu@nvidia.com>
Subject: |FAILURE| pw127355 [PATCH] [v4] lib: set/get max memzone segments
Date: Wed, 24 May 2023 18:03:35 -0700 (PDT) [thread overview]
Message-ID: <646eb3e7.810a0220.e72db.d8c3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-testing
Test-Status: FAILURE
http://dpdk.org/patch/127355
_Testing issues_
Submitter: Ophir Munk <ophirmu@nvidia.com>
Date: Wednesday, May 24 2023 22:25:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c41a103c961ded5a0966652f4daf0a661a947352
127355 --> testing fail
Test environment and result as below:
+--------------------------+----------------+
| Environment | dpdk_unit_test |
+==========================+================+
| Debian 11 (Buster) (ARM) | FAIL |
+--------------------------+----------------+
| Debian Buster | FAIL |
+--------------------------+----------------+
| CentOS Stream 8 | FAIL |
+--------------------------+----------------+
| CentOS Stream 9 | PASS |
+--------------------------+----------------+
| Debian Bullseye | FAIL |
+--------------------------+----------------+
| Fedora 38 | FAIL |
+--------------------------+----------------+
| Fedora 38 (ARM) | FAIL |
+--------------------------+----------------+
| RHEL 7 | PASS |
+--------------------------+----------------+
| Fedora 37 (ARM) | FAIL |
+--------------------------+----------------+
| CentOS Stream 9 (ARM) | PASS |
+--------------------------+----------------+
| openSUSE Leap 15 | PASS |
+--------------------------+----------------+
| Fedora 37 | PASS |
+--------------------------+----------------+
| Ubuntu 20.04 | FAIL |
+--------------------------+----------------+
| RHEL8 | FAIL |
+--------------------------+----------------+
| Ubuntu 22.04 | FAIL |
+--------------------------+----------------+
| Ubuntu 20.04 (ARM) | FAIL |
+--------------------------+----------------+
==== 20 line log output for Ubuntu 20.04 (ARM) (dpdk_unit_test): ====
93/103 DPDK:fast-tests / telemetry_data_autotest OK 0.07 s
94/103 DPDK:fast-tests / table_autotest OK 6.89 s
95/103 DPDK:fast-tests / ring_pmd_autotest OK 0.07 s
96/103 DPDK:fast-tests / event_eth_tx_adapter_autotest OK 1.02 s
97/103 DPDK:fast-tests / bitratestats_autotest OK 0.07 s
98/103 DPDK:fast-tests / latencystats_autotest OK 0.07 s
99/103 DPDK:fast-tests / pdump_autotest OK 5.18 s
100/103 DPDK:fast-tests / vdev_autotest OK 0.07 s
101/103 DPDK:fast-tests / rawdev_autotest OK 0.07 s
102/103 DPDK:fast-tests / compressdev_autotest SKIP 0.07 s
103/103 DPDK:fast-tests / telemetry_all OK 16.51 s
Ok: 96
Expected Fail: 0
Fail: 1
Unexpected Pass: 0
Skipped: 6
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 ====
Debian 11 (Buster) (ARM)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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
Fedora 38 (ARM)
Kernel: Depends on container host
Compiler: clang 16.0.3
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 37 (ARM)
Kernel: Depends on container host
Compiler: gcc 12.3.1
CentOS Stream 9 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 11.3.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
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 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Ubuntu 20.04 (ARM)
Kernel: Container Host Kernel
Compiler: gcc 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26372/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-05-25 1:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 1:03 dpdklab [this message]
[not found] <20230524222550.3538819-1-ophirmu@nvidia.com>
2023-05-24 22:19 ` |FAILURE| pw127355 [PATCH v4] " qemudev
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=646eb3e7.810a0220.e72db.d8c3SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=ophirmu@nvidia.com \
--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).