automatic DPDK test reports
 help / color / mirror / Atom feed
From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>,
	Georgii Tkachuk <georgii.tkachuk@intel.com>,
	Qian Xu <qian.q.xu@intel.com>, Lijuan Tu <lijuan.tu@intel.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-test-reports@iol.unh.edu,
	Bruce Richardson <bruce.richardson@intel.com>
Subject: |FAILURE| pw155761-155762 [PATCH] [v2,2/2] mailmap: sort mailmap
Date: Fri, 08 Aug 2025 15:02:28 -0700 (PDT)	[thread overview]
Message-ID: <689673f4.050a0220.2272ca.cab3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250808210837.518507-3-bruce.richardson@intel.com>

Test-Label: iol-intel-Performance
Test-Status: FAILURE
http://dpdk.org/patch/155762

_Performance Testing issues_

Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Friday, August 08 2025 21:08:34 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:38543d33bd47fc0ee21f59db80a8763620741879

155761-155762 --> performance testing issues

Upstream job id: Template-DTS-Pipeline#239780

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Intel E810 100000 Mbps
Fail/Total: 0/2

Detail performance results: 
+------------+---------+----------+-------------+------------------------------+
| frame_size | txd/rxd | num_cpus | num_threads |  throughput difference from  |
|            |         |          |             |           expected           |
+============+=========+==========+=============+==============================+
| 64         | 512     | 1        | 1           | -0.0%                        |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | 0.1%                         |
+------------+---------+----------+-------------+------------------------------+

Ubuntu 20.04
Kernel: 5.4
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Fail/Total: 0/4

Detail performance results: 
+----------+-------------+---------+------------+------------------------------+
| num_cpus | num_threads | txd/rxd | frame_size |  throughput difference from  |
|          |             |         |            |           expected           |
+==========+=============+=========+============+==============================+
| 1        | 2           | 512     | 64         | -0.1%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 2           | 2048    | 64         | -1.3%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | 2.0%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | -3.9%                        |
+----------+-------------+---------+------------+------------------------------+

Ubuntu 24.04
Kernel: 6.8
Compiler: gcc gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0
NIC: Intel E810 (Arm Grace Server) 100000 Mbps
Fail/Total: 2/2
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         | 512     | 1        | 1           | -31.9%                       |
+------------+---------+----------+-------------+------------------------------+
| 64         | 2048    | 1        | 1           | -24.9%                       |
+------------+---------+----------+-------------+------------------------------+

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2025-08-08 22:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250808210837.518507-3-bruce.richardson@intel.com>
2025-08-08 20:43 ` |SUCCESS| pw155761-155762 [PATCH v2 2/2] " qemudev
2025-08-08 20:48 ` qemudev
2025-08-08 21:07 ` |WARNING| pw155762 " checkpatch
2025-08-08 21:40 ` |PENDING| pw155761-155762 [PATCH] [v2,2/2] " dpdklab
2025-08-08 21:40 ` |SUCCESS| " dpdklab
2025-08-08 21:43 ` |PENDING| " dpdklab
2025-08-08 21:49 ` |SUCCESS| " dpdklab
2025-08-08 22:01 ` dpdklab
2025-08-08 22:01 ` dpdklab
2025-08-08 22:02 ` dpdklab [this message]
2025-08-08 22:02 ` dpdklab
2025-08-08 22:05 ` dpdklab
2025-08-08 22:06 ` dpdklab
2025-08-08 22:09 ` dpdklab
2025-08-08 22:17 ` dpdklab
2025-08-08 22:21 ` dpdklab
2025-08-08 22:26 ` |SUCCESS| pw155762 [PATCH v2 2/2] " 0-day Robot
2025-08-09  1:03 ` |SUCCESS| pw155761-155762 [PATCH] [v2,2/2] " dpdklab
2025-08-09  2:16 ` 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=689673f4.050a0220.2272ca.cab3SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --cc=bruce.richardson@intel.com \
    --cc=dpdk-test-reports@iol.unh.edu \
    --cc=ferruh.yigit@intel.com \
    --cc=georgii.tkachuk@intel.com \
    --cc=lijuan.tu@intel.com \
    --cc=qian.q.xu@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).