From: dpdklab@iol.unh.edu
To: test-report@dpdk.org
Cc: dpdk-test-reports@iol.unh.edu
Subject: |WARNING| pw118172 [PATCH] [v13, 1/1] test-bbdev: unit test extension including for FFT
Date: Thu, 13 Oct 2022 22:39:02 -0400 (EDT) [thread overview]
Message-ID: <20221014023902.96F2C6D509@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 3417 bytes --]
Test-Label: iol-testing
Test-Status: WARNING
http://dpdk.org/patch/118172
_apply patch failure_
Submitter: Nicolas Chautru <nicolas.chautru@intel.com>
Date: Friday, October 14 2022 02:17:54
Applied on: CommitID:a74b1b25136a592c275afbfa6b70771469750aee
Apply patch set 118172 failed:
Checking patch app/test-bbdev/test_bbdev_perf.c...
Hunk #1 succeeded at 129 (offset -8 lines).
Hunk #2 succeeded at 155 (offset -8 lines).
Hunk #3 succeeded at 443 (offset -8 lines).
Hunk #4 succeeded at 995 (offset -70 lines).
Hunk #5 succeeded at 1009 (offset -70 lines).
Hunk #6 succeeded at 1063 (offset -70 lines).
Hunk #7 succeeded at 1810 (offset -70 lines).
Hunk #8 succeeded at 1890 (offset -70 lines).
Hunk #9 succeeded at 2111 (offset -70 lines).
Hunk #10 succeeded at 2196 (offset -70 lines).
Hunk #11 succeeded at 2345 (offset -70 lines).
Hunk #12 succeeded at 2448 (offset -70 lines).
Hunk #13 succeeded at 2561 (offset -70 lines).
Hunk #14 succeeded at 2584 (offset -70 lines).
Hunk #15 succeeded at 2604 (offset -70 lines).
Hunk #16 succeeded at 2672 (offset -70 lines).
Hunk #17 succeeded at 2885 (offset -70 lines).
Hunk #18 succeeded at 2933 (offset -70 lines).
Hunk #19 succeeded at 2959 (offset -70 lines).
Hunk #20 succeeded at 3093 (offset -70 lines).
Hunk #21 succeeded at 3119 (offset -70 lines).
Hunk #22 succeeded at 3349 (offset -70 lines).
Hunk #23 succeeded at 3452 (offset -70 lines).
Hunk #24 succeeded at 3469 (offset -70 lines).
Hunk #25 succeeded at 3484 (offset -70 lines).
Hunk #26 succeeded at 3730 (offset 58 lines).
Hunk #27 succeeded at 3969 (offset -70 lines).
Hunk #28 succeeded at 4272 (offset -70 lines).
Hunk #29 succeeded at 4294 (offset -70 lines).
Hunk #30 succeeded at 4685 (offset -70 lines).
Hunk #31 succeeded at 4804 (offset -70 lines).
Hunk #32 succeeded at 5269 (offset -70 lines).
Checking patch app/test-bbdev/test_bbdev_vector.c...
Checking patch app/test-bbdev/test_bbdev_vector.h...
Checking patch app/test-bbdev/test_vectors/fft_9.data...
Checking patch app/test-bbdev/test_vectors/fft_byp_28.data...
Checking patch doc/guides/rel_notes/release_22_11.rst...
error: while searching for:
Added support for asymmetric crypto algorithms.
See the :doc:`../sample_app_ug/fips_validation` for more details.
Removed Items
-------------
error: patch failed: doc/guides/rel_notes/release_22_11.rst:254
Checking patch doc/guides/tools/testbbdev.rst...
Applied patch app/test-bbdev/test_bbdev_perf.c cleanly.
Applied patch app/test-bbdev/test_bbdev_vector.c cleanly.
Applied patch app/test-bbdev/test_bbdev_vector.h cleanly.
Applied patch app/test-bbdev/test_vectors/fft_9.data cleanly.
Applied patch app/test-bbdev/test_vectors/fft_byp_28.data cleanly.
Applying patch doc/guides/rel_notes/release_22_11.rst with 1 reject...
Rejected hunk #1.
Applied patch doc/guides/tools/testbbdev.rst cleanly.
diff a/doc/guides/rel_notes/release_22_11.rst b/doc/guides/rel_notes/release_22_11.rst (rejected hunks)
@@ -254,6 +254,12 @@ New Features
Added support for asymmetric crypto algorithms.
See the :doc:`../sample_app_ug/fips_validation` for more details.
+* **Updated bbdev test application.**
+
+ Added support for bbdev level unit test for the FFT operations and
+ for Soft-Output options.
+ Also added 2 small test vectors for the FFT operation.
+
Removed Items
-------------
https://lab.dpdk.org/results/dashboard/patchsets/23996/
UNH-IOL DPDK Community Lab
next reply other threads:[~2022-10-14 2:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 2:39 dpdklab [this message]
[not found] <20221014021754.48157-2-nicolas.chautru@intel.com>
2022-10-14 2:19 ` |WARNING| pw118172 [PATCH v13 " checkpatch
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=20221014023902.96F2C6D509@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).