automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Xueming Li <xuemingl@nvidia.com>,
	Christian Ehrhardt <christian.ehrhardt@canonical.com>,
	Kevin Traynor <ktraynor@redhat.com>,
	Luca Boccassi <bluca@debian.org>
Subject: |FAILURE| [GIT MASTER] 7ce7d3341d7e21c2a81f2fea8e451681d7306d77
Date: Tue, 24 Dec 2024 23:31:40 -0800 (PST)	[thread overview]
Message-ID: <676bb4dc.050a0220.25c780.070cSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: tags/v22.11

7ce7d3341d7e21c2a81f2fea8e451681d7306d77 --> testing issues

Upstream job id: Generic-VM-Unit-Test-DPDK#26711

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/tarballs/32045/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

             reply	other threads:[~2024-12-25  7:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-25  7:31 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-24  9:12 dpdklab
2024-12-24  8:04 dpdklab
2024-12-23  7:37 dpdklab
2024-12-23  6:49 dpdklab
2024-12-22  7:32 dpdklab
2024-12-22  7:31 dpdklab
2024-12-21  8:26 dpdklab
2024-12-21  7:58 dpdklab
2024-12-21  7:57 dpdklab
2024-12-21  7:09 dpdklab
2024-12-20  8:54 dpdklab
2024-12-20  8:49 dpdklab
2024-12-20  7:53 dpdklab
2024-12-19  6:54 dpdklab
2024-12-19  6:46 dpdklab
2024-12-19  6:05 dpdklab
2024-12-18 10:52 dpdklab
2024-12-18  1:41 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=676bb4dc.050a0220.25c780.070cSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ktraynor@redhat.com \
    --cc=test-report@dpdk.org \
    --cc=xuemingl@nvidia.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).