automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
	Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Subject: |FAILURE| pw144444 [PATCH] app/test: refactor cryptodev test cases
Date: Wed, 25 Sep 2024 20:26:10 -0700 (PDT)	[thread overview]
Message-ID: <66f4d452.050a0220.38d69a.e100SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240925181525.66119-1-arkadiuszx.kusztal@intel.com>

Test-Label: iol-mellanox-Performance
Test-Status: FAILURE
http://dpdk.org/patch/144444

_Performance Testing issues_

Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Wednesday, September 25 2024 18:15:25 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43

144444 --> performance testing issues

Upstream job id: Template-DTS-Pipeline#183447

Test environment and result as below:

Ubuntu 24.04
Kernel: 6.8.0-45-generic
Compiler: gcc 13.2.0
NIC: NVIDIA Mellanox ConnectX-7 100000 Mbps
Fail/Total: 1/6
Failed cases list:
      - DTS https://dpdklab.iol.unh.edu/results/testcases/1/

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 1024    | 1        | 1           | -1.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 128        | 1024    | 1        | 1           | -0.8%                        |
+------------+---------+----------+-------------+------------------------------+
| 256        | 1024    | 1        | 1           | -2.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 512        | 1024    | 1        | 1           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 1024       | 1024    | 1        | 1           | 0.3%                         |
+------------+---------+----------+-------------+------------------------------+
| 1518       | 1024    | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 24.04
Kernel: 6.8.0-45-generic
Compiler: gcc 13.2.0
NIC: Mellanox ConnectX-6 Lx 25000 Mbps
Fail/Total: 0/1

Detail performance results: 
The measurement deltas are not ready yet! Please check back later.

To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31140/

UNH-IOL DPDK Community Lab

To manage your email subscriptions, visit: 
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/

  parent reply	other threads:[~2024-09-26  3:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240925181525.66119-1-arkadiuszx.kusztal@intel.com>
2024-09-25 19:03 ` |SUCCESS| " qemudev
2024-09-25 19:08 ` qemudev
2024-09-25 19:31 ` |WARNING| " checkpatch
2024-09-25 20:23 ` |SUCCESS| " 0-day Robot
2024-09-26  3:26 ` dpdklab [this message]
2024-09-26  3:28 ` dpdklab
2024-09-26  3:33 ` dpdklab
2024-09-26  3:33 ` dpdklab
2024-09-26  3:39 ` |FAILURE| " dpdklab
2024-09-26  3:43 ` |SUCCESS| " dpdklab
2024-09-26  3:45 ` dpdklab
2024-09-26  3:50 ` dpdklab
2024-09-26  3:55 ` dpdklab
2024-09-26  4:04 ` dpdklab
2024-09-26  4:39 ` dpdklab
2024-09-26  4:58 ` |PENDING| " dpdklab
2024-09-26  5:55 ` dpdklab
2024-09-26  7:48 ` |SUCCESS| " dpdklab
2024-09-26  8:00 ` dpdklab
2024-09-26  8:14 ` dpdklab
2024-09-26  8:39 ` dpdklab
2024-09-26 12:23 ` dpdklab

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=66f4d452.050a0220.38d69a.e100SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=arkadiuszx.kusztal@intel.com \
    --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).