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, Zaiyu Wang <zaiyuwang@trustnetic.com>
Subject: |FAILURE| pw154701-154715 [PATCH] [v2,15/15] doc: update for txgbe
Date: Wed, 25 Jun 2025 10:10:16 -0700 (PDT)	[thread overview]
Message-ID: <685c2d78.170a0220.18e623.6526SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250625125047.18072-16-zaiyuwang@trustnetic.com>

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

_Testing issues_

Submitter: Zaiyu Wang <zaiyuwang@trustnetic.com>
Date: Wednesday, June 25 2025 12:50:47 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:62a35bbb247e608e235a04ff2941488bc1a78941

154701-154715 --> testing issues

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

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | FAIL           |
+---------------------+----------------+
| Ubuntu 20.04        | FAIL           |
+---------------------+----------------+

==== Unit test summary for Ubuntu 20.04 (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

Ubuntu 20.04
	Kernel: 4.19
	Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33501/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-06-25 17:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250625125047.18072-16-zaiyuwang@trustnetic.com>
2025-06-25 12:28 ` |SUCCESS| pw154701-154715 [PATCH v2 15/15] " qemudev
2025-06-25 12:33 ` qemudev
2025-06-25 12:52 ` |SUCCESS| pw154715 " checkpatch
2025-06-25 14:03 ` |FAILURE| " 0-day Robot
2025-06-25 14:35 ` |SUCCESS| pw154701-154715 [PATCH] [v2,15/15] " dpdklab
2025-06-25 14:52 ` dpdklab
2025-06-25 14:53 ` dpdklab
2025-06-25 15:11 ` dpdklab
2025-06-25 15:15 ` dpdklab
2025-06-25 15:16 ` |FAILURE| " dpdklab
2025-06-25 15:24 ` dpdklab
2025-06-25 15:46 ` |SUCCESS| " dpdklab
2025-06-25 15:49 ` |PENDING| " dpdklab
2025-06-25 17:07 ` |FAILURE| " dpdklab
2025-06-25 17:10 ` dpdklab [this message]
2025-06-25 19:44 ` dpdklab
2025-06-25 19:46 ` |WARNING| " dpdklab
2025-06-25 21:13 ` |SUCCESS| " dpdklab
2025-06-25 21:13 ` dpdklab
2025-06-25 21:14 ` dpdklab
2025-06-25 22:04 ` |FAILURE| " dpdklab
2025-06-25 22:05 ` dpdklab
2025-06-25 22:06 ` dpdklab
2025-06-25 22:06 ` dpdklab
2025-06-25 22:07 ` dpdklab
2025-06-25 22:07 ` dpdklab
2025-06-25 22:08 ` dpdklab
2025-06-25 22:08 ` dpdklab
2025-06-25 22:09 ` dpdklab
2025-06-25 22:09 ` 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=685c2d78.170a0220.18e623.6526SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=zaiyuwang@trustnetic.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).