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
Subject: |WARNING| pw140838 [PATCH] [v5] eventdev/crypto: restore opaque fiel
Date: Thu, 06 Jun 2024 16:19:02 -0700 (PDT)	[thread overview]
Message-ID: <666243e6.170a0220.1aecc1.5eddSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240606134800.2049198-1-ganapati.kundapura@intel.com>

Test-Label: iol-compile-amd64-testing
Test-Status: WARNING
http://dpdk.org/patch/140838

_Testing issues_

Submitter: Ganapati Kundapura <ganapati.kundapura@intel.com>
Date: Thursday, June 06 2024 13:48:00 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:229d27a82792fab339d78b9bec26a0f395674d43

140838 --> testing issues

Test environment and result as below:

+---------------------+----------------------+--------------------+-------------------+
|     Environment     | dpdk_mingw64_compile | dpdk_meson_compile | dpdk_msvc_compile |
+=====================+======================+====================+===================+
| Windows Server 2019 | FAIL                 | PASS               | SKIPPED           |
+---------------------+----------------------+--------------------+-------------------+
| Windows Server 2022 | PASS                 | SKIPPED            | PASS              |
+---------------------+----------------------+--------------------+-------------------+
| FreeBSD 13.3        | SKIPPED              | PASS               | SKIPPED           |
+---------------------+----------------------+--------------------+-------------------+
| FreeBSD 14.0        | SKIPPED              | PASS               | SKIPPED           |
+---------------------+----------------------+--------------------+-------------------+

==== 20 line log output for Windows Server 2019 (dpdk_mingw64_compile): ====
 --- Failed to get log output --- 
==== 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

FreeBSD 13.3
	Kernel: 13.3-RELEASE-p1
	Compiler: clang 17.0.6

FreeBSD 14.0
	Kernel: 14.0
	Compiler: clang 16.0.6

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-06 23:19 UTC|newest]

Thread overview: 102+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240606134800.2049198-1-ganapati.kundapura@intel.com>
2024-06-06 13:21 ` |SUCCESS| pw140838 [PATCH v5] eventdev/crypto: restore opaque field between dequeue and enqueue qemudev
2024-06-06 13:25 ` qemudev
2024-06-06 13:49 ` checkpatch
2024-06-06 14:47 ` 0-day Robot
2024-06-06 22:49 ` |SUCCESS| pw140838 [PATCH] [v5] eventdev/crypto: restore opaque fiel dpdklab
2024-06-06 22:49 ` dpdklab
2024-06-06 22:49 ` dpdklab
2024-06-06 23:15 ` dpdklab
2024-06-06 23:15 ` dpdklab
2024-06-06 23:16 ` |WARNING| " dpdklab
2024-06-06 23:17 ` dpdklab
2024-06-06 23:17 ` |SUCCESS| " dpdklab
2024-06-06 23:18 ` dpdklab
2024-06-06 23:19 ` dpdklab [this message]
2024-06-06 23:19 ` |WARNING| " dpdklab
2024-06-06 23:19 ` dpdklab
2024-06-06 23:19 ` |SUCCESS| " dpdklab
2024-06-06 23:20 ` dpdklab
2024-06-06 23:20 ` dpdklab
2024-06-06 23:20 ` dpdklab
2024-06-06 23:21 ` dpdklab
2024-06-06 23:21 ` dpdklab
2024-06-06 23:21 ` |WARNING| " dpdklab
2024-06-06 23:21 ` |SUCCESS| " dpdklab
2024-06-06 23:22 ` dpdklab
2024-06-06 23:22 ` dpdklab
2024-06-06 23:23 ` dpdklab
2024-06-06 23:23 ` dpdklab
2024-06-06 23:23 ` dpdklab
2024-06-06 23:23 ` dpdklab
2024-06-06 23:24 ` dpdklab
2024-06-06 23:24 ` dpdklab
2024-06-06 23:25 ` dpdklab
2024-06-06 23:25 ` dpdklab
2024-06-06 23:25 ` dpdklab
2024-06-06 23:25 ` dpdklab
2024-06-06 23:26 ` dpdklab
2024-06-06 23:26 ` dpdklab
2024-06-06 23:26 ` dpdklab
2024-06-06 23:27 ` dpdklab
2024-06-06 23:27 ` dpdklab
2024-06-06 23:27 ` dpdklab
2024-06-06 23:27 ` |WARNING| " dpdklab
2024-06-06 23:28 ` |SUCCESS| " dpdklab
2024-06-06 23:28 ` dpdklab
2024-06-06 23:29 ` dpdklab
2024-06-06 23:30 ` |WARNING| " dpdklab
2024-06-06 23:31 ` |SUCCESS| " dpdklab
2024-06-06 23:31 ` dpdklab
2024-06-06 23:33 ` dpdklab
2024-06-06 23:34 ` dpdklab
2024-06-06 23:34 ` dpdklab
2024-06-06 23:35 ` dpdklab
2024-06-06 23:35 ` dpdklab
2024-06-06 23:36 ` |WARNING| " dpdklab
2024-06-06 23:36 ` |SUCCESS| " dpdklab
2024-06-06 23:38 ` dpdklab
2024-06-06 23:38 ` dpdklab
2024-06-06 23:39 ` |WARNING| " dpdklab
2024-06-06 23:40 ` dpdklab
2024-06-06 23:41 ` |SUCCESS| " dpdklab
2024-06-06 23:42 ` dpdklab
2024-06-06 23:42 ` |WARNING| " dpdklab
2024-06-06 23:42 ` |SUCCESS| " dpdklab
2024-06-06 23:43 ` dpdklab
2024-06-06 23:43 ` dpdklab
2024-06-06 23:45 ` dpdklab
2024-06-06 23:45 ` |WARNING| " dpdklab
2024-06-06 23:45 ` |SUCCESS| " dpdklab
2024-06-06 23:47 ` |WARNING| " dpdklab
2024-06-06 23:47 ` |SUCCESS| " dpdklab
2024-06-06 23:49 ` |WARNING| " dpdklab
2024-06-06 23:49 ` |SUCCESS| " dpdklab
2024-06-06 23:49 ` dpdklab
2024-06-06 23:49 ` |WARNING| " dpdklab
2024-06-06 23:50 ` |SUCCESS| " dpdklab
2024-06-06 23:50 ` |WARNING| " dpdklab
2024-06-06 23:52 ` |SUCCESS| " dpdklab
2024-06-06 23:52 ` |WARNING| " dpdklab
2024-06-06 23:53 ` |SUCCESS| " dpdklab
2024-06-06 23:55 ` dpdklab
2024-06-06 23:55 ` dpdklab
2024-06-06 23:56 ` dpdklab
2024-06-06 23:58 ` |WARNING| " dpdklab
2024-06-07  0:00 ` |SUCCESS| " dpdklab
2024-06-07  0:01 ` dpdklab
2024-06-07  0:06 ` dpdklab
2024-06-07  0:06 ` dpdklab
2024-06-07  0:06 ` |WARNING| " dpdklab
2024-06-07  0:06 ` |SUCCESS| " dpdklab
2024-06-07  0:07 ` |WARNING| " dpdklab
2024-06-07  0:07 ` |SUCCESS| " dpdklab
2024-06-07  0:10 ` dpdklab
2024-06-07  0:10 ` dpdklab
2024-06-07  0:11 ` dpdklab
2024-06-07  0:11 ` dpdklab
2024-06-07  0:11 ` dpdklab
2024-06-07  0:12 ` dpdklab
2024-06-07  0:14 ` dpdklab
2024-06-07  0:25 ` dpdklab
2024-06-07  0:45 ` dpdklab
2024-06-07 14:32 ` 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=666243e6.170a0220.1aecc1.5eddSMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=dpdk-test-reports@iol.unh.edu \
    --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).