From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Stephen Hemminger <stephen@networkplumber.org>
Subject: |FAILURE| pw144132-144146 [PATCH] [v22,15/15] doc: add release note
Date: Tue, 17 Sep 2024 20:58:54 -0700 (PDT) [thread overview]
Message-ID: <66ea4ffe.050a0220.5f1ee.217cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240917203828.414701-16-stephen@networkplumber.org>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/144146
_Testing issues_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tuesday, September 17 2024 20:35:57
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
144132-144146 --> testing issues
Upstream job id: Generic-VM-Unit-Test-DPDK#25282
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | FAIL |
+---------------------+----------------+
| CentOS Stream 9 | 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
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31052/
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-09-18 3:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240917203828.414701-16-stephen@networkplumber.org>
2024-09-17 20:17 ` |SUCCESS| pw144132-144146 [PATCH v22 15/15] doc: add release note about log library qemudev
2024-09-17 20:22 ` qemudev
2024-09-17 20:45 ` |SUCCESS| pw144146 " checkpatch
2024-09-17 21:24 ` |FAILURE| " 0-day Robot
2024-09-17 23:35 ` |SUCCESS| pw144132-144146 [PATCH] [v22,15/15] doc: add release note dpdklab
2024-09-18 0:38 ` dpdklab
2024-09-18 0:57 ` dpdklab
2024-09-18 1:06 ` dpdklab
2024-09-18 1:33 ` dpdklab
2024-09-18 3:58 ` dpdklab [this message]
2024-09-18 4:25 ` |PENDING| " dpdklab
2024-09-18 4:36 ` |FAILURE| " dpdklab
2024-09-18 4:39 ` dpdklab
2024-09-18 4:40 ` dpdklab
2024-09-18 5:29 ` |SUCCESS| " dpdklab
2024-09-18 5:46 ` dpdklab
2024-09-18 5:48 ` dpdklab
2024-09-18 6:03 ` |FAILURE| " dpdklab
2024-09-18 6:43 ` dpdklab
2024-09-18 10:38 ` |SUCCESS| " dpdklab
2024-09-18 15:07 ` dpdklab
2024-09-22 10:24 ` dpdklab
2024-09-22 10:36 ` 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=66ea4ffe.050a0220.5f1ee.217cSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=stephen@networkplumber.org \
--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).