From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Niall Meade <niall.meade@intel.com>
Subject: |FAILURE| pw145844 [PATCH] [v3] hash: separate param checks in hash
Date: Tue, 15 Oct 2024 00:43:43 -0700 (PDT) [thread overview]
Message-ID: <670e1d2f.170a0220.173268.1e9fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241014101916.2043948-1-niall.meade@intel.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/145844
_Testing issues_
Submitter: Niall Meade <niall.meade@intel.com>
Date: Monday, October 14 2024 10:19:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:5f7b98189de733080656989d63b0e7ffd249830a
145844 --> testing issues
Upstream job id: Generic-VM-Unit-Test-DPDK#25671
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | FAIL |
+---------------------+----------------+
| RHEL9 | PEND |
+---------------------+----------------+
| RHEL8 | PEND |
+---------------------+----------------+
| Ubuntu 20.04 | 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 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
RHEL9
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
RHEL8
Kernel: Depends on container host
Compiler: gcc 8.5.0 20210514 (Red Hat 8.5.0-22)
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Ubuntu 22.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 24.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31464/
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-10-15 7:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241014101916.2043948-1-niall.meade@intel.com>
2024-10-14 10:19 ` |SUCCESS| pw145844 [PATCH v3] hash: separate param checks in hash create func qemudev
2024-10-14 10:21 ` checkpatch
2024-10-14 10:23 ` qemudev
2024-10-14 12:02 ` 0-day Robot
2024-10-15 0:26 ` |SUCCESS| pw145844 [PATCH] [v3] hash: separate param checks in hash dpdklab
2024-10-15 0:51 ` dpdklab
2024-10-15 1:28 ` dpdklab
2024-10-15 2:43 ` dpdklab
2024-10-15 7:43 ` dpdklab [this message]
2024-10-15 9:23 ` |FAILURE| " dpdklab
2024-10-15 9:31 ` dpdklab
2024-10-15 11:15 ` |WARNING| " 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=670e1d2f.170a0220.173268.1e9fSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=niall.meade@intel.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).