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
Subject: |PENDING| pw142670 [PATCH] test/event: fix missing schedule type ass
Date: Tue, 23 Jul 2024 15:23:33 -0700 (PDT)	[thread overview]
Message-ID: <66a02d65.050a0220.3106d8.1584SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240723193212.2625-1-pbhagavatula@marvell.com>

Test-Label: iol-intel-Performance
Test-Status: PENDING
http://dpdk.org/patch/142670

_Performance Testing pending_

Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Tuesday, July 23 2024 19:32:12 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:fa8d2f7f28524a6c8defa3dcd94f5aa131aae084

142670 --> performance testing pending

Upstream job id: Template-DTS-Pipeline#170124

Test environment and result as below:

Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Fail/Total: 0/1

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

22.04
Kernel: 5.15.0-94-generic
Compiler: gcc 11.4.0
NIC: Intel E810 100000 Mbps
Fail/Total: 0/4

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

Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 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         | 7.0%                         |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 512     | 64         | -5.8%                        |
+----------+-------------+---------+------------+------------------------------+
| 1        | 1           | 2048    | 64         | -3.2%                        |
+----------+-------------+---------+------------+------------------------------+

Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 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/30598/

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-07-23 22:23 UTC|newest]

Thread overview: 113+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240723193212.2625-1-pbhagavatula@marvell.com>
2024-07-23 19:12 ` |SUCCESS| pw142670 [PATCH] test/event: fix missing schedule type assignment qemudev
2024-07-23 19:17 ` qemudev
2024-07-23 19:33 ` checkpatch
2024-07-23 20:23 ` 0-day Robot
2024-07-23 22:15 ` |SUCCESS| pw142670 [PATCH] test/event: fix missing schedule type ass dpdklab
2024-07-23 22:18 ` dpdklab
2024-07-23 22:20 ` |PENDING| " dpdklab
2024-07-23 22:23 ` dpdklab [this message]
2024-07-23 22:25 ` dpdklab
2024-07-23 22:27 ` |SUCCESS| " dpdklab
2024-07-23 22:28 ` dpdklab
2024-07-23 22:29 ` |PENDING| " dpdklab
2024-07-23 22:31 ` dpdklab
2024-07-23 22:34 ` dpdklab
2024-07-23 22:34 ` |SUCCESS| " dpdklab
2024-07-23 22:37 ` dpdklab
2024-07-23 22:38 ` dpdklab
2024-07-23 22:39 ` |PENDING| " dpdklab
2024-07-23 22:41 ` dpdklab
2024-07-23 22:41 ` |SUCCESS| " dpdklab
2024-07-23 22:41 ` |PENDING| " dpdklab
2024-07-23 22:41 ` |SUCCESS| " dpdklab
2024-07-23 22:41 ` |PENDING| " dpdklab
2024-07-23 22:43 ` dpdklab
2024-07-23 22:45 ` |SUCCESS| " dpdklab
2024-07-23 22:46 ` |PENDING| " dpdklab
2024-07-23 22:46 ` dpdklab
2024-07-23 22:46 ` |SUCCESS| " dpdklab
2024-07-23 22:46 ` |PENDING| " dpdklab
2024-07-23 22:47 ` dpdklab
2024-07-23 22:48 ` |SUCCESS| " dpdklab
2024-07-23 22:50 ` |PENDING| " dpdklab
2024-07-23 22:53 ` dpdklab
2024-07-23 22:55 ` dpdklab
2024-07-23 22:56 ` dpdklab
2024-07-23 22:56 ` dpdklab
2024-07-23 22:56 ` dpdklab
2024-07-23 22:59 ` dpdklab
2024-07-23 22:59 ` dpdklab
2024-07-23 23:01 ` dpdklab
2024-07-23 23:01 ` dpdklab
2024-07-23 23:02 ` dpdklab
2024-07-23 23:02 ` dpdklab
2024-07-23 23:03 ` dpdklab
2024-07-23 23:03 ` dpdklab
2024-07-23 23:03 ` dpdklab
2024-07-23 23:04 ` dpdklab
2024-07-23 23:04 ` |SUCCESS| " dpdklab
2024-07-23 23:05 ` |PENDING| " dpdklab
2024-07-23 23:05 ` dpdklab
2024-07-23 23:06 ` dpdklab
2024-07-23 23:06 ` dpdklab
2024-07-23 23:06 ` dpdklab
2024-07-23 23:07 ` |FAILURE| " dpdklab
2024-07-23 23:07 ` |PENDING| " dpdklab
2024-07-23 23:07 ` dpdklab
2024-07-23 23:07 ` |FAILURE| " dpdklab
2024-07-23 23:07 ` |PENDING| " dpdklab
2024-07-23 23:09 ` |FAILURE| " dpdklab
2024-07-23 23:09 ` |PENDING| " dpdklab
2024-07-23 23:10 ` dpdklab
2024-07-23 23:11 ` |SUCCESS| " dpdklab
2024-07-23 23:11 ` |PENDING| " dpdklab
2024-07-23 23:11 ` dpdklab
2024-07-23 23:13 ` dpdklab
2024-07-23 23:14 ` dpdklab
2024-07-23 23:14 ` dpdklab
2024-07-23 23:14 ` dpdklab
2024-07-23 23:14 ` |SUCCESS| " dpdklab
2024-07-23 23:14 ` |PENDING| " dpdklab
2024-07-23 23:14 ` dpdklab
2024-07-23 23:15 ` |SUCCESS| " dpdklab
2024-07-23 23:16 ` |PENDING| " dpdklab
2024-07-23 23:16 ` dpdklab
2024-07-23 23:16 ` |FAILURE| " dpdklab
2024-07-23 23:18 ` |PENDING| " dpdklab
2024-07-23 23:20 ` dpdklab
2024-07-23 23:20 ` dpdklab
2024-07-23 23:21 ` dpdklab
2024-07-23 23:24 ` dpdklab
2024-07-23 23:24 ` dpdklab
2024-07-23 23:25 ` dpdklab
2024-07-23 23:25 ` |FAILURE| " dpdklab
2024-07-23 23:25 ` |PENDING| " dpdklab
2024-07-23 23:25 ` dpdklab
2024-07-23 23:25 ` dpdklab
2024-07-23 23:25 ` dpdklab
2024-07-23 23:26 ` dpdklab
2024-07-23 23:26 ` dpdklab
2024-07-23 23:26 ` dpdklab
2024-07-23 23:29 ` dpdklab
2024-07-23 23:30 ` dpdklab
2024-07-23 23:31 ` |FAILURE| " dpdklab
2024-07-23 23:32 ` |PENDING| " dpdklab
2024-07-23 23:32 ` dpdklab
2024-07-23 23:34 ` dpdklab
2024-07-23 23:36 ` dpdklab
2024-07-23 23:36 ` |FAILURE| " dpdklab
2024-07-23 23:36 ` |PENDING| " dpdklab
2024-07-23 23:37 ` |SUCCESS| " dpdklab
2024-07-23 23:38 ` |FAILURE| " dpdklab
2024-07-23 23:38 ` |PENDING| " dpdklab
2024-07-23 23:38 ` |FAILURE| " dpdklab
2024-07-23 23:41 ` |PENDING| " dpdklab
2024-07-23 23:42 ` dpdklab
2024-07-23 23:43 ` |FAILURE| " dpdklab
2024-07-23 23:46 ` dpdklab
2024-07-23 23:46 ` dpdklab
2024-07-23 23:46 ` |SUCCESS| " dpdklab
2024-07-24  0:22 ` |PENDING| " dpdklab
2024-07-24  0:32 ` dpdklab
2024-07-24  0:46 ` |SUCCESS| " dpdklab
2024-07-25  6:06 ` 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=66a02d65.050a0220.3106d8.1584SMTPIN_ADDED_MISSING@mx.google.com \
    --to=dpdklab@iol.unh.edu \
    --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).