From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Jie Hai <haijie1@huawei.com>
Subject: |FAILURE| pw147360-147369 [PATCH] [v4,13/13] devtools: check for som
Date: Sat, 26 Oct 2024 23:06:52 -0700 (PDT) [thread overview]
Message-ID: <671dd87c.170a0220.91298.dc8fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241026101451.29135-14-haijie1@huawei.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/147369
_Testing issues_
Submitter: Jie Hai <haijie1@huawei.com>
Date: Saturday, October 26 2024 10:14:51
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2721319d1b5f9197846111e781f449ef91583f58
147360-147369 --> testing issues
Upstream job id: Generic-VM-Unit-Test-DPDK#25923
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | FAIL |
+---------------------+----------------+
==== 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31695/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2024-10-27 6:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241026101451.29135-14-haijie1@huawei.com>
2024-10-26 9:55 ` |SUCCESS| pw147360-147369 [PATCH v4 13/13] devtools: check for some reentrant function qemudev
2024-10-26 10:00 ` qemudev
2024-10-26 10:28 ` |SUCCESS| pw147369 " checkpatch
2024-10-26 10:58 ` |PENDING| pw147360-147369 [PATCH] [v4,13/13] devtools: check for som dpdklab
2024-10-26 11:01 ` |SUCCESS| " dpdklab
2024-10-26 11:03 ` dpdklab
2024-10-26 11:07 ` dpdklab
2024-10-26 11:16 ` dpdklab
2024-10-26 11:17 ` dpdklab
2024-10-26 11:21 ` dpdklab
2024-10-26 11:21 ` dpdklab
2024-10-26 11:23 ` dpdklab
2024-10-26 11:26 ` |SUCCESS| pw147369 [PATCH v4 13/13] devtools: check for some reentrant function 0-day Robot
2024-10-26 15:07 ` |SUCCESS| pw147360-147369 [PATCH] [v4,13/13] devtools: check for som dpdklab
2024-10-27 6:06 ` dpdklab [this message]
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=671dd87c.170a0220.91298.dc8fSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=haijie1@huawei.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).