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,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: |FAILURE| pw147346-147358 [PATCH] [v29,13/13] doc: add release note
Date: Sat, 26 Oct 2024 23:06:01 -0700 (PDT)	[thread overview]
Message-ID: <671dd849.050a0220.155ad2.f781SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241025214625.62876-14-stephen@networkplumber.org>

Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/147358

_Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Friday, October 25 2024 21:45:18 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2721319d1b5f9197846111e781f449ef91583f58

147346-147358 --> testing issues

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

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/31693/

UNH-IOL DPDK Community Lab

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

      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] <20241025214625.62876-14-stephen@networkplumber.org>
2024-10-25 21:21 ` |SUCCESS| pw147346-147358 [PATCH v29 13/13] doc: add release note about log library qemudev
2024-10-25 21:26 ` qemudev
2024-10-25 21:49 ` |WARNING| pw147358 " checkpatch
2024-10-25 23:06 ` |SUCCESS| " 0-day Robot
2024-10-26  7:53 ` |SUCCESS| pw147346-147358 [PATCH] [v29,13/13] doc: add release note dpdklab
2024-10-26  8:05 ` dpdklab
2024-10-26  8:07 ` dpdklab
2024-10-26  8:09 ` |PENDING| " dpdklab
2024-10-26  8:09 ` |SUCCESS| " dpdklab
2024-10-26  8:13 ` dpdklab
2024-10-26  8:18 ` dpdklab
2024-10-26  8:24 ` dpdklab
2024-10-26  9:18 ` dpdklab
2024-10-26 14:49 ` 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=671dd849.050a0220.155ad2.f781SMTPIN_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).