From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Wathsala Vithanage <wathsala.vithanage@arm.com>
Subject: |FAILURE| pw142417 [PATCH] [RFC,v2] ethdev: an API for cache stashin
Date: Tue, 16 Jul 2024 04:55:15 -0700 (PDT) [thread overview]
Message-ID: <66965fa3.170a0220.7403e.9371SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240715221141.16153-1-wathsala.vithanage@arm.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/142417
_Testing issues_
Submitter: Wathsala Vithanage <wathsala.vithanage@arm.com>
Date: Monday, July 15 2024 22:11:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084
142417 --> testing issues
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | FAIL |
+---------------------+----------------+
| Windows Server 2022 | FAIL |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Bullseye | PEND |
+---------------------+----------------+
| Debian 12 | PEND |
+---------------------+----------------+
| Fedora 38 (Clang) | PEND |
+---------------------+----------------+
| Fedora 37 | PEND |
+---------------------+----------------+
| Fedora 38 | PEND |
+---------------------+----------------+
| Fedora 39 | PEND |
+---------------------+----------------+
| Fedora 39 (Clang) | PEND |
+---------------------+----------------+
| Fedora 40 | PEND |
+---------------------+----------------+
| Fedora 40 (Clang) | PEND |
+---------------------+----------------+
| openSUSE Leap 15 | PEND |
+---------------------+----------------+
| Ubuntu 20.04 | PEND |
+---------------------+----------------+
| RHEL8 | PEND |
+---------------------+----------------+
| RHEL9 | PEND |
+---------------------+----------------+
| Ubuntu 22.04 | PEND |
+---------------------+----------------+
| Ubuntu 24.04 | PEND |
+---------------------+----------------+
==== Unit test summary for Windows Server 2022 (dpdk_unit_test): ====
Failed to get the unit test results.
Displaying the unit test results is not supported for some environments,
such as our aarch32 testing, where meson is not used to run the tests.
Download the logs available on our CI site.
==== End log output ====
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Debian 12
Kernel: Container Host Kernel
Compiler: gcc 12.2.0
Fedora 38 (Clang)
Kernel: Depends on container host
Compiler: clang 16.0.6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 39
Kernel: Depends on container host
Compiler: gcc 13.2.1
Fedora 39 (Clang)
Kernel: Depends on container host
Compiler: clang 17.0.6
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.1.1
Fedora 40 (Clang)
Kernel: Depends on container host
Compiler: clang 18.1.6
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
RHEL8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-20)
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.4.1
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
Ubuntu 24.04
Kernel: 5.4.0-167-generic
Compiler: gcc 13.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30524/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-07-16 11:55 UTC|newest]
Thread overview: 113+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240715221141.16153-1-wathsala.vithanage@arm.com>
2024-07-15 21:46 ` |SUCCESS| pw142417 [RFC v2] ethdev: an API for cache stashing hints qemudev
2024-07-15 21:50 ` qemudev
2024-07-15 22:13 ` |WARNING| " checkpatch
2024-07-15 23:24 ` |FAILURE| " 0-day Robot
2024-07-16 8:58 ` |PENDING| pw142417 [PATCH] [RFC,v2] ethdev: an API for cache stashin dpdklab
2024-07-16 9:04 ` dpdklab
2024-07-16 9:12 ` |SUCCESS| " dpdklab
2024-07-16 9:17 ` dpdklab
2024-07-16 9:23 ` dpdklab
2024-07-16 9:29 ` dpdklab
2024-07-16 9:32 ` dpdklab
2024-07-16 9:45 ` dpdklab
2024-07-16 10:04 ` |PENDING| " dpdklab
2024-07-16 10:12 ` |SUCCESS| " dpdklab
2024-07-16 10:18 ` |WARNING| " dpdklab
2024-07-16 10:20 ` dpdklab
2024-07-16 10:29 ` dpdklab
2024-07-16 10:31 ` dpdklab
2024-07-16 10:32 ` dpdklab
2024-07-16 10:36 ` dpdklab
2024-07-16 10:37 ` dpdklab
2024-07-16 10:37 ` dpdklab
2024-07-16 10:37 ` dpdklab
2024-07-16 10:43 ` dpdklab
2024-07-16 10:46 ` dpdklab
2024-07-16 10:46 ` |SUCCESS| " dpdklab
2024-07-16 10:50 ` |WARNING| " dpdklab
2024-07-16 10:58 ` dpdklab
2024-07-16 10:58 ` |FAILURE| " dpdklab
2024-07-16 11:09 ` |WARNING| " dpdklab
2024-07-16 11:14 ` |FAILURE| " dpdklab
2024-07-16 11:15 ` dpdklab
2024-07-16 11:18 ` dpdklab
2024-07-16 11:19 ` dpdklab
2024-07-16 11:19 ` dpdklab
2024-07-16 11:21 ` dpdklab
2024-07-16 11:21 ` dpdklab
2024-07-16 11:31 ` |PENDING| " dpdklab
2024-07-16 11:36 ` dpdklab
2024-07-16 11:41 ` dpdklab
2024-07-16 11:42 ` dpdklab
2024-07-16 11:45 ` dpdklab
2024-07-16 11:47 ` |FAILURE| " dpdklab
2024-07-16 11:51 ` |PENDING| " dpdklab
2024-07-16 11:51 ` dpdklab
2024-07-16 11:52 ` dpdklab
2024-07-16 11:52 ` |FAILURE| " dpdklab
2024-07-16 11:55 ` dpdklab [this message]
2024-07-16 11:55 ` dpdklab
2024-07-16 11:56 ` dpdklab
2024-07-16 11:57 ` dpdklab
2024-07-16 11:58 ` dpdklab
2024-07-16 11:59 ` dpdklab
2024-07-16 12:01 ` dpdklab
2024-07-16 12:02 ` dpdklab
2024-07-16 12:03 ` dpdklab
2024-07-16 12:04 ` dpdklab
2024-07-16 12:05 ` dpdklab
2024-07-16 12:06 ` dpdklab
2024-07-16 12:07 ` |PENDING| " dpdklab
2024-07-16 12:08 ` |FAILURE| " dpdklab
2024-07-16 12:09 ` |PENDING| " dpdklab
2024-07-16 12:09 ` |FAILURE| " dpdklab
2024-07-16 12:09 ` dpdklab
2024-07-16 12:10 ` dpdklab
2024-07-16 12:10 ` |PENDING| " dpdklab
2024-07-16 12:11 ` |FAILURE| " dpdklab
2024-07-16 12:12 ` |PENDING| " dpdklab
2024-07-16 12:14 ` |FAILURE| " dpdklab
2024-07-16 12:15 ` dpdklab
2024-07-16 12:15 ` |PENDING| " dpdklab
2024-07-16 12:18 ` |FAILURE| " dpdklab
2024-07-16 12:18 ` |PENDING| " dpdklab
2024-07-16 12:19 ` |FAILURE| " dpdklab
2024-07-16 12:19 ` dpdklab
2024-07-16 12:23 ` dpdklab
2024-07-16 12:23 ` |PENDING| " dpdklab
2024-07-16 12:23 ` |FAILURE| " dpdklab
2024-07-16 12:25 ` dpdklab
2024-07-16 12:26 ` dpdklab
2024-07-16 12:27 ` |PENDING| " dpdklab
2024-07-16 12:27 ` |FAILURE| " dpdklab
2024-07-16 12:30 ` |PENDING| " dpdklab
2024-07-16 12:30 ` |FAILURE| " dpdklab
2024-07-16 12:31 ` |PENDING| " dpdklab
2024-07-16 12:31 ` |FAILURE| " dpdklab
2024-07-16 12:33 ` |PENDING| " dpdklab
2024-07-16 12:34 ` |FAILURE| " dpdklab
2024-07-16 12:38 ` |PENDING| " dpdklab
2024-07-16 12:39 ` dpdklab
2024-07-16 12:41 ` dpdklab
2024-07-16 12:43 ` dpdklab
2024-07-16 12:46 ` dpdklab
2024-07-16 12:49 ` |FAILURE| " dpdklab
2024-07-16 12:50 ` |PENDING| " dpdklab
2024-07-16 12:54 ` dpdklab
2024-07-16 12:55 ` dpdklab
2024-07-16 12:57 ` dpdklab
2024-07-16 12:58 ` dpdklab
2024-07-16 13:03 ` dpdklab
2024-07-16 13:05 ` dpdklab
2024-07-16 13:06 ` dpdklab
2024-07-16 13:08 ` dpdklab
2024-07-16 13:08 ` dpdklab
2024-07-16 13:10 ` dpdklab
2024-07-16 13:11 ` |SUCCESS| " dpdklab
2024-07-16 13:32 ` dpdklab
2024-07-16 21:17 ` dpdklab
2024-07-16 22:12 ` dpdklab
2024-07-16 22:16 ` dpdklab
2024-07-16 22:20 ` dpdklab
2024-07-16 22:39 ` dpdklab
2024-07-16 22:43 ` 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=66965fa3.170a0220.7403e.9371SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=wathsala.vithanage@arm.com \
/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).