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| pw142769-142771 [PATCH] [v2,3/3] test: remove unused resou
Date: Tue, 30 Jul 2024 23:34:33 -0700 (PDT)	[thread overview]
Message-ID: <66a9daf9.b00a0220.33d08a.cfb3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240731042141.76985-4-stephen@networkplumber.org>

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

_Testing issues_

Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, July 31 2024 04:20:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:1d245ca8239d947258b3ae7cc4d8df97ef527852

142769-142771 --> testing issues

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

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PEND           |
+---------------------+----------------+
| Windows Server 2022 | FAIL           |
+---------------------+----------------+
| CentOS Stream 8     | PEND           |
+---------------------+----------------+
| 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 2019
	Kernel: 10.0.17763
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

Windows Server 2022
	Kernel: 10.0.20348.2031
	Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9

CentOS Stream 8
	Kernel: 5.4.0-167-generic
	Compiler: gcc 8.5.0 20210514

CentOS Stream 9
	Kernel: 5.4.0-167-generic
	Compiler: gcc 11.4.1 20230605

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-31  7:07 UTC|newest]

Thread overview: 113+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240731042141.76985-4-stephen@networkplumber.org>
2024-07-31  3:57 ` |SUCCESS| pw142769-142771 [PATCH v2 3/3] test: remove unused resource API qemudev
2024-07-31  4:01 ` qemudev
2024-07-31  4:24 ` |SUCCESS| pw142771 " checkpatch
2024-07-31  5:22 ` 0-day Robot
2024-07-31  5:31 ` |SUCCESS| pw142769-142771 [PATCH] [v2,3/3] test: remove unused resou dpdklab
2024-07-31  5:47 ` dpdklab
2024-07-31  5:52 ` dpdklab
2024-07-31  5:55 ` dpdklab
2024-07-31  6:03 ` dpdklab
2024-07-31  6:05 ` dpdklab
2024-07-31  6:09 ` dpdklab
2024-07-31  6:16 ` dpdklab
2024-07-31  6:24 ` |FAILURE| " dpdklab
2024-07-31  6:26 ` dpdklab
2024-07-31  6:26 ` dpdklab
2024-07-31  6:29 ` dpdklab
2024-07-31  6:30 ` dpdklab
2024-07-31  6:31 ` dpdklab
2024-07-31  6:32 ` |PENDING| " dpdklab
2024-07-31  6:34 ` dpdklab
2024-07-31  6:34 ` dpdklab [this message]
2024-07-31  6:38 ` |FAILURE| " dpdklab
2024-07-31  6:43 ` |PENDING| " dpdklab
2024-07-31  6:44 ` dpdklab
2024-07-31  6:48 ` |SUCCESS| " dpdklab
2024-07-31  6:51 ` |PENDING| " dpdklab
2024-07-31  6:52 ` dpdklab
2024-07-31  6:52 ` dpdklab
2024-07-31  6:57 ` dpdklab
2024-07-31  6:59 ` dpdklab
2024-07-31  7:00 ` dpdklab
2024-07-31  7:05 ` |SUCCESS| " dpdklab
2024-07-31  7:10 ` |PENDING| " dpdklab
2024-07-31  7:11 ` dpdklab
2024-07-31  7:19 ` dpdklab
2024-07-31  7:24 ` dpdklab
2024-07-31  7:28 ` dpdklab
2024-07-31  7:29 ` dpdklab
2024-07-31  7:31 ` dpdklab
2024-07-31  7:32 ` dpdklab
2024-07-31  7:33 ` dpdklab
2024-07-31  7:33 ` dpdklab
2024-07-31  7:34 ` dpdklab
2024-07-31  7:37 ` dpdklab
2024-07-31  7:38 ` dpdklab
2024-07-31  7:39 ` dpdklab
2024-07-31  7:39 ` dpdklab
2024-07-31  7:41 ` |SUCCESS| " dpdklab
2024-07-31  7:41 ` |PENDING| " dpdklab
2024-07-31  7:42 ` dpdklab
2024-07-31  7:48 ` dpdklab
2024-07-31  7:49 ` dpdklab
2024-07-31  7:55 ` dpdklab
2024-07-31  7:57 ` dpdklab
2024-07-31  7:59 ` dpdklab
2024-07-31  8:02 ` dpdklab
2024-07-31  8:03 ` dpdklab
2024-07-31  8:04 ` dpdklab
2024-07-31  8:06 ` dpdklab
2024-07-31  8:06 ` dpdklab
2024-07-31  8:07 ` dpdklab
2024-07-31  8:08 ` dpdklab
2024-07-31  8:09 ` dpdklab
2024-07-31  8:10 ` dpdklab
2024-07-31  8:13 ` dpdklab
2024-07-31  8:13 ` |SUCCESS| " dpdklab
2024-07-31  8:14 ` |PENDING| " dpdklab
2024-07-31  8:25 ` |SUCCESS| " dpdklab
2024-07-31  8:26 ` |FAILURE| " dpdklab
2024-07-31  8:27 ` dpdklab
2024-07-31  8:28 ` dpdklab
2024-07-31  8:38 ` dpdklab
2024-07-31  8:39 ` dpdklab
2024-07-31  8:40 ` dpdklab
2024-07-31  8:40 ` |SUCCESS| " dpdklab
2024-07-31  8:42 ` |FAILURE| " dpdklab
2024-07-31  8:42 ` dpdklab
2024-07-31  8:42 ` dpdklab
2024-07-31  8:42 ` dpdklab
2024-07-31  8:42 ` dpdklab
2024-07-31  8:46 ` |SUCCESS| " dpdklab
2024-07-31  8:46 ` |FAILURE| " dpdklab
2024-07-31  8:47 ` dpdklab
2024-07-31  8:47 ` dpdklab
2024-07-31  8:47 ` dpdklab
2024-07-31  8:47 ` dpdklab
2024-07-31  8:49 ` dpdklab
2024-07-31  8:51 ` |SUCCESS| " dpdklab
2024-07-31  8:51 ` |FAILURE| " dpdklab
2024-07-31  8:51 ` dpdklab
2024-07-31  8:52 ` dpdklab
2024-07-31  8:52 ` dpdklab
2024-07-31  8:52 ` dpdklab
2024-07-31  8:53 ` |PENDING| " dpdklab
2024-07-31  8:53 ` |FAILURE| " dpdklab
2024-07-31  8:55 ` dpdklab
2024-07-31  8:55 ` dpdklab
2024-07-31  8:57 ` |SUCCESS| " dpdklab
2024-07-31  8:58 ` |FAILURE| " dpdklab
2024-07-31  8:59 ` dpdklab
2024-07-31  9:00 ` dpdklab
2024-07-31  9:01 ` dpdklab
2024-07-31  9:01 ` dpdklab
2024-07-31  9:02 ` dpdklab
2024-07-31  9:04 ` dpdklab
2024-07-31  9:04 ` |PENDING| " dpdklab
2024-07-31  9:05 ` |FAILURE| " dpdklab
2024-07-31  9:11 ` |PENDING| " dpdklab
2024-07-31  9:17 ` |SUCCESS| " dpdklab
2024-07-31  9:31 ` dpdklab
2024-07-31  9:31 ` dpdklab
2024-07-31  9:33 ` dpdklab
2024-07-31 10:26 ` 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=66a9daf9.b00a0220.33d08a.cfb3SMTPIN_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).