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, Vipin Varghese <vipin.varghese@amd.com>
Subject: |FAILURE| pw142397 [PATCH] app/testpmd: improve sse based macswap
Date: Sat, 13 Jul 2024 09:01:57 -0700 (PDT)	[thread overview]
Message-ID: <6692a4f5.050a0220.50975.5cfdSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240713151949.832-1-vipin.varghese@amd.com>

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

_Testing issues_

Submitter: Vipin Varghese <vipin.varghese@amd.com>
Date: Saturday, July 13 2024 15:19:49 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084

142397 --> testing issues

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PEND           |
+---------------------+----------------+
| 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 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

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

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-13 16:02 UTC|newest]

Thread overview: 114+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240713151949.832-1-vipin.varghese@amd.com>
2024-07-13 14:53 ` |SUCCESS| " qemudev
2024-07-13 14:57 ` qemudev
2024-07-13 15:21 ` checkpatch
2024-07-13 15:49 ` dpdklab
2024-07-13 15:50 ` |PENDING| " dpdklab
2024-07-13 15:50 ` dpdklab
2024-07-13 15:53 ` dpdklab
2024-07-13 15:54 ` |SUCCESS| " dpdklab
2024-07-13 15:55 ` |FAILURE| " dpdklab
2024-07-13 15:55 ` dpdklab
2024-07-13 15:57 ` |SUCCESS| " dpdklab
2024-07-13 15:58 ` dpdklab
2024-07-13 15:58 ` dpdklab
2024-07-13 15:58 ` |PENDING| " dpdklab
2024-07-13 15:58 ` |FAILURE| " dpdklab
2024-07-13 15:59 ` dpdklab
2024-07-13 16:01 ` |PENDING| " dpdklab
2024-07-13 16:01 ` |FAILURE| " dpdklab
2024-07-13 16:01 ` dpdklab [this message]
2024-07-13 16:03 ` |PENDING| " dpdklab
2024-07-13 16:04 ` dpdklab
2024-07-13 16:04 ` |FAILURE| " dpdklab
2024-07-13 16:05 ` |PENDING| " dpdklab
2024-07-13 16:06 ` |WARNING| " dpdklab
2024-07-13 16:06 ` |FAILURE| " dpdklab
2024-07-13 16:06 ` |PENDING| " dpdklab
2024-07-13 16:07 ` |SUCCESS| " dpdklab
2024-07-13 16:07 ` |FAILURE| " dpdklab
2024-07-13 16:07 ` |PENDING| " dpdklab
2024-07-13 16:08 ` dpdklab
2024-07-13 16:08 ` |FAILURE| " dpdklab
2024-07-13 16:09 ` |PENDING| " dpdklab
2024-07-13 16:09 ` dpdklab
2024-07-13 16:09 ` |WARNING| " dpdklab
2024-07-13 16:09 ` dpdklab
2024-07-13 16:10 ` |FAILURE| " dpdklab
2024-07-13 16:10 ` |PENDING| " dpdklab
2024-07-13 16:10 ` |SUCCESS| " dpdklab
2024-07-13 16:11 ` |WARNING| " dpdklab
2024-07-13 16:11 ` dpdklab
2024-07-13 16:11 ` |PENDING| " dpdklab
2024-07-13 16:14 ` |WARNING| " dpdklab
2024-07-13 16:15 ` |SUCCESS| " dpdklab
2024-07-13 16:16 ` |WARNING| " dpdklab
2024-07-13 16:16 ` |PENDING| " dpdklab
2024-07-13 16:16 ` |WARNING| " dpdklab
2024-07-13 16:19 ` dpdklab
2024-07-13 16:19 ` |PENDING| " dpdklab
2024-07-13 16:19 ` |WARNING| " dpdklab
2024-07-13 16:20 ` dpdklab
2024-07-13 16:20 ` |PENDING| " dpdklab
2024-07-13 16:21 ` |FAILURE| " dpdklab
2024-07-13 16:21 ` |PENDING| " dpdklab
2024-07-13 16:22 ` |FAILURE| " dpdklab
2024-07-13 16:22 ` dpdklab
2024-07-13 16:23 ` 0-day Robot
2024-07-13 16:24 ` dpdklab
2024-07-13 16:25 ` |PENDING| " dpdklab
2024-07-13 16:25 ` |FAILURE| " dpdklab
2024-07-13 16:26 ` |PENDING| " dpdklab
2024-07-13 16:26 ` dpdklab
2024-07-13 16:27 ` |FAILURE| " dpdklab
2024-07-13 16:29 ` |PENDING| " dpdklab
2024-07-13 16:29 ` |WARNING| " dpdklab
2024-07-13 16:30 ` |PENDING| " dpdklab
2024-07-13 16:34 ` dpdklab
2024-07-13 16:35 ` |FAILURE| " dpdklab
2024-07-13 16:36 ` dpdklab
2024-07-13 16:37 ` |PENDING| " dpdklab
2024-07-13 16:37 ` dpdklab
2024-07-13 16:38 ` |FAILURE| " dpdklab
2024-07-13 16:38 ` dpdklab
2024-07-13 16:40 ` dpdklab
2024-07-13 16:40 ` dpdklab
2024-07-13 16:41 ` dpdklab
2024-07-13 16:41 ` |PENDING| " dpdklab
2024-07-13 16:41 ` |FAILURE| " dpdklab
2024-07-13 16:41 ` dpdklab
2024-07-13 16:42 ` dpdklab
2024-07-13 16:42 ` |PENDING| " dpdklab
2024-07-13 16:42 ` |FAILURE| " dpdklab
2024-07-13 16:42 ` dpdklab
2024-07-13 16:43 ` dpdklab
2024-07-13 16:43 ` dpdklab
2024-07-13 16:43 ` dpdklab
2024-07-13 16:45 ` dpdklab
2024-07-13 16:46 ` |PENDING| " dpdklab
2024-07-13 16:46 ` |FAILURE| " dpdklab
2024-07-13 16:47 ` |PENDING| " dpdklab
2024-07-13 16:48 ` |FAILURE| " dpdklab
2024-07-13 16:49 ` |PENDING| " dpdklab
2024-07-13 16:49 ` |SUCCESS| " dpdklab
2024-07-13 16:49 ` |PENDING| " dpdklab
2024-07-13 16:49 ` |FAILURE| " dpdklab
2024-07-13 16:51 ` |PENDING| " dpdklab
2024-07-13 16:51 ` |FAILURE| " dpdklab
2024-07-13 16:52 ` dpdklab
2024-07-13 16:53 ` |PENDING| " dpdklab
2024-07-13 16:53 ` dpdklab
2024-07-13 16:53 ` |FAILURE| " dpdklab
2024-07-13 16:55 ` |PENDING| " dpdklab
2024-07-13 16:55 ` |FAILURE| " dpdklab
2024-07-13 16:55 ` dpdklab
2024-07-13 16:55 ` |SUCCESS| " dpdklab
2024-07-13 16:55 ` |FAILURE| " dpdklab
2024-07-13 16:59 ` dpdklab
2024-07-13 17:23 ` |PENDING| " dpdklab
2024-07-13 17:24 ` dpdklab
2024-07-13 17:27 ` |SUCCESS| " dpdklab
2024-07-15 23:57 ` dpdklab
2024-07-16  0:01 ` dpdklab
2024-07-16  0:05 ` dpdklab
2024-07-16  0:25 ` dpdklab
2024-07-16  0:30 ` 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=6692a4f5.050a0220.50975.5cfdSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=test-report@dpdk.org \
    --cc=vipin.varghese@amd.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).