DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/cryptodev Bug 1487] blockcipher_test_case_run() does not log test_msg
Date: Fri, 12 Jul 2024 13:15:37 +0000	[thread overview]
Message-ID: <bug-1487-3@http.bugs.dpdk.org/> (raw)

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

https://bugs.dpdk.org/show_bug.cgi?id=1487

            Bug ID: 1487
           Summary: blockcipher_test_case_run() does not log test_msg
           Product: DPDK
           Version: 24.07
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: cryptodev
          Assignee: dev@dpdk.org
          Reporter: jack.bond-preston@arm.com
  Target Milestone: ---

app/test/test_cryptodev_blockcipher.c:blockcipher_test_case_run() allocates a
test_msg string and the test function it calls writes useful output to this.
However, the string is never used, so this useful logging is never provided -
even in the event of (unexpected) failures.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 2710 bytes --]

                 reply	other threads:[~2024-07-12 13:15 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=bug-1487-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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).