From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, "Nayak,
Nishikanta" <nishikanta.nayak@intel.com>
Subject: |FAILURE| pw137335-137338 [PATCH] [v4,4/4] test/cryptodev: add tests
Date: Tue, 05 Mar 2024 20:12:14 -0800 (PST) [thread overview]
Message-ID: <65e7ed1e.170a0220.ac4db.1625SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227094006.565697-5-nishikanta.nayak@intel.com>
Test-Label: iol-broadcom-Performance
Test-Status: FAILURE
http://dpdk.org/patch/137338
_Performance Testing issues_
Submitter: Nayak, Nishikanta <nishikanta.nayak@intel.com>
Date: Tuesday, February 27 2024 09:40:06
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137335-137338 --> performance testing fail
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 1/2
Detail performance results:
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads | throughput difference from |
| | | | | expected |
+============+=========+==========+=============+==============================+
| 64 | 512 | 1 | 1 | -1.4% |
+------------+---------+----------+-------------+------------------------------+
| 64 | 2048 | 1 | 1 | -5.2% |
+------------+---------+----------+-------------+------------------------------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29282/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-06 4:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240227094006.565697-5-nishikanta.nayak@intel.com>
2024-02-27 9:27 ` |SUCCESS| pw137335-137338 [PATCH v4 4/4] test/cryptodev: add tests for GCM with AAD qemudev
2024-02-27 9:31 ` qemudev
2024-02-27 9:43 ` |SUCCESS| pw137338 " checkpatch
2024-02-27 10:45 ` 0-day Robot
2024-02-27 20:08 ` |SUCCESS| pw137335-137338 [PATCH] [v4,4/4] test/cryptodev: add tests dpdklab
2024-02-27 21:21 ` dpdklab
2024-02-28 4:44 ` dpdklab
2024-02-28 5:15 ` dpdklab
2024-02-28 5:27 ` dpdklab
2024-02-28 11:05 ` dpdklab
2024-02-29 9:07 ` |FAILURE| " dpdklab
2024-02-29 9:12 ` |SUCCESS| " dpdklab
2024-02-29 9:17 ` dpdklab
2024-02-29 9:22 ` dpdklab
2024-03-06 4:12 ` dpdklab [this message]
2024-02-27 17:45 |FAILURE| " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-27 16:58 dpdklab
2024-02-27 16:39 dpdklab
2024-02-27 16:26 dpdklab
2024-02-27 16:23 dpdklab
2024-02-27 16:22 dpdklab
2024-02-27 16:19 dpdklab
2024-02-27 16:19 dpdklab
2024-02-27 16:13 dpdklab
2024-02-27 16:12 dpdklab
2024-02-27 16:12 dpdklab
2024-02-27 16:11 dpdklab
2024-02-27 16:10 dpdklab
2024-02-27 16:10 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=65e7ed1e.170a0220.ac4db.1625SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=nishikanta.nayak@intel.com \
--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).