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: |WARNING| pw129778 [PATCH] security: hide security context
Date: Tue, 01 Aug 2023 07:13:22 -0700 (PDT)	[thread overview]
Message-ID: <64c91302.050a0220.8c613.9199SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_apply patch failure_

Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Tuesday, August 01 2023 08:10:47 
Applied on: CommitID:12fcafcd62286933e6b167b14856d21f642efa5f
Apply patch set 129778 failed:

Checking patch app/test-crypto-perf/cperf_ops.c...
Checking patch app/test-crypto-perf/cperf_test_latency.c...
Checking patch app/test-crypto-perf/cperf_test_pmd_cyclecount.c...
Checking patch app/test-crypto-perf/cperf_test_throughput.c...
Checking patch app/test-crypto-perf/cperf_test_verify.c...
Checking patch app/test-security-perf/test_security_perf.c...
Checking patch app/test/test_cryptodev.c...
Checking patch app/test/test_cryptodev_security_ipsec.c...
Checking patch app/test/test_cryptodev_security_ipsec.h...
Checking patch app/test/test_security_inline_macsec.c...
Checking patch app/test/test_security_inline_proto.c...
Checking patch examples/ipsec-secgw/ipsec-secgw.c...
Checking patch examples/ipsec-secgw/ipsec.c...
Checking patch examples/ipsec-secgw/ipsec.h...
Checking patch examples/ipsec-secgw/ipsec_worker.c...
Checking patch examples/ipsec-secgw/ipsec_worker.h...
Checking patch examples/l2fwd-macsec/main.c...
error: examples/l2fwd-macsec/main.c: does not exist in index
Checking patch lib/security/rte_security.c...
Checking patch lib/security/rte_security.h...
Checking patch lib/security/rte_security_driver.h...
Applied patch app/test-crypto-perf/cperf_ops.c cleanly.
Applied patch app/test-crypto-perf/cperf_test_latency.c cleanly.
Applied patch app/test-crypto-perf/cperf_test_pmd_cyclecount.c cleanly.
Applied patch app/test-crypto-perf/cperf_test_throughput.c cleanly.
Applied patch app/test-crypto-perf/cperf_test_verify.c cleanly.
Applied patch app/test-security-perf/test_security_perf.c cleanly.
Applied patch app/test/test_cryptodev.c cleanly.
Applied patch app/test/test_cryptodev_security_ipsec.c cleanly.
Applied patch app/test/test_cryptodev_security_ipsec.h cleanly.
Applied patch app/test/test_security_inline_macsec.c cleanly.
Applied patch app/test/test_security_inline_proto.c cleanly.
Applied patch examples/ipsec-secgw/ipsec-secgw.c cleanly.
Applied patch examples/ipsec-secgw/ipsec.c cleanly.
Applied patch examples/ipsec-secgw/ipsec.h cleanly.
Applied patch examples/ipsec-secgw/ipsec_worker.c cleanly.
Applied patch examples/ipsec-secgw/ipsec_worker.h cleanly.
Applied patch lib/security/rte_security.c cleanly.
Applied patch lib/security/rte_security.h cleanly.
Applied patch lib/security/rte_security_driver.h cleanly.
hint: Use 'git am --show-current-patch' to see the failed patch

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

UNH-IOL DPDK Community Lab

             reply	other threads:[~2023-08-01 14:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 14:13 dpdklab [this message]
     [not found] <20230801081047.1219935-1-gakhil@marvell.com>
2023-08-01  8:05 ` qemudev

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=64c91302.050a0220.8c613.9199SMTPIN_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).