test suite reviews and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: dts@dpdk.org
Cc: probb@iol.unh.edu
Subject: [PATCH] tests/TestSuite_crypto_perf_cryptodev_perf: fix output parsing
Date: Mon, 16 Sep 2024 11:25:15 +0200	[thread overview]
Message-ID: <20240916092515.1851927-1-david.marchand@redhat.com> (raw)

The parsing of the test results was considering too many lines.

It was not an issue as the extra inspected line was an empty line.
Following fixes on the qat driver logs, this triggers a parsing error.

Fixes: a3c915c1a3b9 ("tests/crypto_perf_cryptodev_perf: optimize parse output")
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
 tests/TestSuite_crypto_perf_cryptodev_perf.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/TestSuite_crypto_perf_cryptodev_perf.py b/tests/TestSuite_crypto_perf_cryptodev_perf.py
index 0531b9c6..633dd637 100644
--- a/tests/TestSuite_crypto_perf_cryptodev_perf.py
+++ b/tests/TestSuite_crypto_perf_cryptodev_perf.py
@@ -252,7 +252,7 @@ class TestCryptoPerfCryptodevPerf(TestCase):
                 if lines[line_index].startswith("    lcore id"):
                     self.logger.debug("data output line from: " + str(line_index))
                     break
-            data_line = line_index - 2
+            data_line = line_index - 1
 
             results = []
             pattern = re.compile(r"\s+")
-- 
2.46.0


             reply	other threads:[~2024-09-16  9:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16  9:25 David Marchand [this message]
2024-09-17 21:19 ` Patrick Robb
2024-09-18  7:17 ` David Marchand

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=20240916092515.1851927-1-david.marchand@redhat.com \
    --to=david.marchand@redhat.com \
    --cc=dts@dpdk.org \
    --cc=probb@iol.unh.edu \
    /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).