automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: [dpdk-test-report] |WARNING| pw98951 [PATCH] app/test: enable crypto unit tests on Windows
Date: Wed, 15 Sep 2021 13:59:29 -0400 (EDT)	[thread overview]
Message-ID: <20210915175929.B8B4AB0FE@noxus.dpdklab.iol.unh.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 2697 bytes --]

Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/98951

_apply patch failure_

Submitter: Tal Shnaiderman <talshn@nvidia.com>
Date: Wednesday, September 15 2021 17:16:49 
Applied on: CommitID:1c91ed5cdde164ca319c2c3b0ba5b4643db8e614
Apply patch set 98951 failed:

Checking patch app/test/meson.build...
Hunk #1 succeeded at 32 (offset 10 lines).
error: while searching for:
        'bitratestats',
        'cfgfile',
        'cmdline',
        'efd',
        'ethdev',
        'hash',

error: patch failed: app/test/meson.build:92
Hunk #3 succeeded at 190 (offset 80 lines).
error: while searching for:
            'test_bpf.c',
            'test_cksum.c',
            'test_cmdline_ipaddr.c',
            'test_cryptodev.c',
            'test_cryptodev_asym.c',
            'test_cryptodev_blockcipher.c',
            'test_cryptodev_security_pdcp.c',
            'test_debug.c',
            'test_distributor.c',
            'test_distributor_perf.c',

error: patch failed: app/test/meson.build:183
error: while searching for:
    test_deps += [
            'acl',
            'bpf',
            'cryptodev',
            'distributor',
            'eventdev',
            'fib',

error: patch failed: app/test/meson.build:244
error: while searching for:
            'pipeline',
            'port',
            'rawdev',
            'security',
    ]

    fast_tests += [

error: patch failed: app/test/meson.build:256
Applying patch app/test/meson.build with 4 rejects...
Hunk #1 applied cleanly.
Rejected hunk #2.
Hunk #3 applied cleanly.
Rejected hunk #4.
Rejected hunk #5.
Rejected hunk #6.
diff a/app/test/meson.build b/app/test/meson.build	(rejected hunks)
@@ -92,6 +96,7 @@ test_deps = [
         'bitratestats',
         'cfgfile',
         'cmdline',
+        'cryptodev',
         'efd',
         'ethdev',
         'hash',
@@ -183,10 +189,6 @@ if not is_windows
             'test_bpf.c',
             'test_cksum.c',
             'test_cmdline_ipaddr.c',
-            'test_cryptodev.c',
-            'test_cryptodev_asym.c',
-            'test_cryptodev_blockcipher.c',
-            'test_cryptodev_security_pdcp.c',
             'test_debug.c',
             'test_distributor.c',
             'test_distributor_perf.c',
@@ -244,7 +246,6 @@ if not is_windows
     test_deps += [
             'acl',
             'bpf',
-            'cryptodev',
             'distributor',
             'eventdev',
             'fib',
@@ -256,7 +257,6 @@ if not is_windows
             'pipeline',
             'port',
             'rawdev',
-            'security',
     ]
 
     fast_tests += [

https://lab.dpdk.org/results/dashboard/patchsets/18781/

UNH-IOL DPDK Community Lab

                 reply	other threads:[~2021-09-15 17:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210915175929.B8B4AB0FE@noxus.dpdklab.iol.unh.edu \
    --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).