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,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Ferruh Yigit <ferruh.yigit@amd.com>
Subject: |FAILURE| [GIT MASTER] dccd6b7c68116a1cc044856aa35928e044640a8d
Date: Thu, 15 Feb 2024 00:25:47 -0800 (PST)	[thread overview]
Message-ID: <65cdca8b.050a0220.23510.297dSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Testing issues_

Branch: dpdk-next-net

dccd6b7c68116a1cc044856aa35928e044640a8d --> testing fail

Test environment and result as below:

+---------------------+----------------+
|     Environment     | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | FAIL           |
+---------------------+----------------+

==== 20 line log output for Windows Server 2019 (dpdk_unit_test): ====
\07\06\0/\08\04\0 \0D\0P\0D\0K\0:\0f\0a\0s\0t\0-\0t\0e\0s\0t\0s\0 \0/\0 \0t\0e\0l\0e\0m\0e\0t\0r\0y\0_\0d\0a\0t\0a\0_\0a\0u\0t\0o\0t\0e\0s\0t\0 \0 \0 \0 \0 \0 \0 \0 \0S\0K\0I\0P\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \00\0.\01\05\0s\0 \0 \0 \0e\0x\0i\0t\0 \0s\0t\0a\0t\0u\0s\0 \07\07\0
\0
\07\07\0/\08\04\0 \0D\0P\0D\0K\0:\0f\0a\0s\0t\0-\0t\0e\0s\0t\0s\0 \0/\0 \0t\0e\0l\0e\0m\0e\0t\0r\0y\0_\0j\0s\0o\0n\0_\0a\0u\0t\0o\0t\0e\0s\0t\0 \0 \0 \0 \0 \0 \0 \0 \0O\0K\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \00\0.\04\05\0s\0
\0
\07\08\0/\08\04\0 \0D\0P\0D\0K\0:\0f\0a\0s\0t\0-\0t\0e\0s\0t\0s\0 \0/\0 \0t\0h\0a\0s\0h\0_\0a\0u\0t\0o\0t\0e\0s\0t\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0O\0K\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \00\0.\04\01\0s\0
\0
\07\09\0/\08\04\0 \0D\0P\0D\0K\0:\0f\0a\0s\0t\0-\0t\0e\0s\0t\0s\0 \0/\0 \0t\0h\0r\0e\0a\0d\0s\0_\0a\0u\0t\0o\0t\0e\0s\0t\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0O\0K\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \01\0.\06\02\0s\0
\0
\08\00\0/\08\04\0 \0D\0P\0D\0K\0:\0f\0a\0s\0t\0-\0t\0e\0s\0t\0s\0 \0/\0 \0t\0i\0c\0k\0e\0t\0l\0o\0c\0k\0_\0a\0u\0t\0o\0t\0e\0s\0t\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0O\0K\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \00\0.\01\09\0s\0
\0
\08\01\0/\08\04\0 \0D\0P\0D\0K\0:\0f\0a\0s\0t\0-\0t\0e\0s\0t\0s\0 \0/\0 \0t\0i\0m\0e\0r\0_\0a\0u\0t\0o\0t\0e\0s\0t\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0O\0K\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \04\0.\02\01\0s\0
\0
\08\02\0/\08\04\0 \0D\0P\0D\0K\0:\0f\0a\0s\0t\0-\0t\0e\0s\0t\0s\0 \0/\0 \0t\0r\0a\0c\0e\0_\0a\0u\0t\0o\0t\0e\0s\0t\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0S\0K\0I\0P\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \00\0.\01\04\0s\0 \0 \0 \0e\0x\0i\0t\0 \0s\0t\0a\0t\0u\0s\0 \07\07\0
\0
\08\03\0/\08\04\0 \0D\0P\0D\0K\0:\0f\0a\0s\0t\0-\0t\0e\0s\0t\0s\0 \0/\0 \0v\0d\0e\0v\0_\0a\0u\0t\0o\0t\0e\0s\0t\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0O\0K\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \00\0.\04\02\0s\0
\0
\08\04\0/\08\04\0 \0D\0P\0D\0K\0:\0f\0a\0s\0t\0-\0t\0e\0s\0t\0s\0 \0/\0 \0v\0e\0r\0s\0i\0o\0n\0_\0a\0u\0t\0o\0t\0e\0s\0t\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0O\0K\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \00\0.\02\00\0s\0
\0
\0
\0
\0
\0
\0O\0k\0:\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \06\04\0 \0 \0
\0
\0E\0x\0p\0e\0c\0t\0e\0d\0 \0F\0a\0i\0l\0:\0 \0 \0 \0 \0 \0 \00\0 \0 \0 \0
\0
\0F\0a\0i\0l\0:\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \01\0 \0 \0 \0
\0
\0U\0n\0e\0x\0p\0e\0c\0t\0e\0d\0 \0P\0a\0s\0s\0:\0 \0 \0 \0 \00\0 \0 \0 \0
\0
\0S\0k\0i\0p\0p\0e\0d\0:\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \01\09\0 \0 \0
\0
\0T\0i\0m\0e\0o\0u\0t\0:\0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \00\0 \0 \0 \0
\0
\0
\0
\0F\0u\0l\0l\0 \0l\0o\0g\0 \0w\0r\0i\0t\0t\0e\0n\0 \0t\0o\0 \0C\0:\0\\0U\0s\0e\0r\0s\0\\0b\0u\0i\0l\0d\0e\0r\0\\0j\0e\0n\0k\0i\0n\0s\0\\0w\0o\0r\0k\0s\0p\0a\0c\0e\0\\0G\0e\0n\0e\0r\0i\0c\0-\0V\0M\0-\0U\0n\0i\0t\0-\0T\0e\0s\0t\0-\0D\0P\0D\0K\0\\0d\0p\0d\0k\0\\0b\0u\0i\0l\0d\0\\0m\0e\0s\0o\0n\0-\0l\0o\0g\0s\0\\0t\0e\0s\0t\0l\0o\0g\0.\0t\0x\0t\0
\0
\0
==== End log output ====

Windows Server 2019
	Kernel: 10.0
	Compiler: clang 14.0 and gcc 8.1.0 (MinGW)

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/28016/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-15  8:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-15  8:25 dpdklab [this message]
2024-02-15  8:40 dpdklab
2024-02-15  8:44 dpdklab
2024-02-15  8:56 dpdklab
2024-02-15  8:59 dpdklab
2024-02-15  8:59 dpdklab
2024-02-15  9:00 dpdklab
2024-02-15  9:04 dpdklab
2024-02-15  9:05 dpdklab
2024-02-15  9:06 dpdklab
2024-02-15  9:07 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=65cdca8b.050a0220.23510.297dSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@amd.com \
    --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).