From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 23826459AC; Mon, 16 Sep 2024 11:25:33 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 08CCB4025F; Mon, 16 Sep 2024 11:25:33 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 3FE3D40041 for ; Mon, 16 Sep 2024 11:25:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1726478731; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=uz2F6730Db4RBG+4m/5uMm28PlJZWVVyGZnLKYPbhfQ=; b=b/B8/uhZHVPluyFYVDAhCBmuQ3czAu8wf1IZBG5WxvKkGEHHnOADcwuZ8hKS1ZEMiauDTq hrIQ780sHJ/hF93d2dwGFqL70b/xNI/fv50LY33w2CbBV/3ljLY9CgxMG33BTnScTEg8xQ 3ah2n3XNh/zILYGyDXt13/m7Et/ddEE= Received: from mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-49-en0v74x_OySAhMMPAAUoQA-1; Mon, 16 Sep 2024 05:25:28 -0400 X-MC-Unique: en0v74x_OySAhMMPAAUoQA-1 Received: from mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-03.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id 1A0471955F40; Mon, 16 Sep 2024 09:25:27 +0000 (UTC) Received: from dmarchan.redhat.com (unknown [10.45.225.123]) by mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 8C8A730001AB; Mon, 16 Sep 2024 09:25:25 +0000 (UTC) From: David Marchand 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 Message-ID: <20240916092515.1851927-1-david.marchand@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.4 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII"; x-default=true X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org 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 --- 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