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: |SUCCESS| pw141952-141954 [PATCH] [3/3] test/bpf: add extra test cas
Date: Thu, 27 Jun 2024 12:44:26 -0700 (PDT)	[thread overview]
Message-ID: <667dc11a.050a0220.8e3ca.0e86SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240627115531.1440-4-konstantin.v.ananyev@yandex.ru>

Test-Label: iol-broadcom-Performance
Test-Status: SUCCESS
http://dpdk.org/patch/141954

_Performance Testing PASS_

Submitter: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Date: Thursday, June 27 2024 11:55:31 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:eeb4b1d1f491b53c3024e0a9e8839acf514122cd

141952-141954 --> performance testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller 16d7 25 Mbps
Target: Unknown
Fail/Total: 0/3

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

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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-06-27 19:44 UTC|newest]

Thread overview: 111+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240627115531.1440-4-konstantin.v.ananyev@yandex.ru>
2024-06-27 11:33 ` |SUCCESS| pw141952-141954 [PATCH 3/3] test/bpf: add extra test cases for bpf convert qemudev
2024-06-27 11:37 ` qemudev
2024-06-27 12:00 ` |SUCCESS| pw141954 " checkpatch
2024-06-27 12:46 ` |FAILURE| " 0-day Robot
2024-06-27 14:32 ` |SUCCESS| pw141952-141954 [PATCH] [3/3] test/bpf: add extra test cas dpdklab
2024-06-27 15:39 ` dpdklab
2024-06-27 15:52 ` dpdklab
2024-06-27 16:10 ` dpdklab
2024-06-27 16:24 ` dpdklab
2024-06-27 17:08 ` dpdklab
2024-06-27 17:33 ` |WARNING| " dpdklab
2024-06-27 17:35 ` dpdklab
2024-06-27 17:38 ` dpdklab
2024-06-27 17:39 ` dpdklab
2024-06-27 17:45 ` dpdklab
2024-06-27 17:46 ` dpdklab
2024-06-27 17:49 ` dpdklab
2024-06-27 17:53 ` dpdklab
2024-06-27 18:00 ` dpdklab
2024-06-27 18:03 ` dpdklab
2024-06-27 18:09 ` dpdklab
2024-06-27 18:11 ` |SUCCESS| " dpdklab
2024-06-27 18:11 ` |WARNING| " dpdklab
2024-06-27 18:12 ` dpdklab
2024-06-27 18:19 ` |SUCCESS| " dpdklab
2024-06-27 18:27 ` |WARNING| " dpdklab
2024-06-27 18:32 ` |SUCCESS| " dpdklab
2024-06-27 18:40 ` |WARNING| " dpdklab
2024-06-27 19:44 ` dpdklab [this message]
2024-06-27 19:53 ` |SUCCESS| " dpdklab
2024-06-27 20:27 ` dpdklab
2024-06-27 20:44 ` |FAILURE| " dpdklab
2024-06-27 20:45 ` dpdklab
2024-06-27 20:46 ` dpdklab
2024-06-27 20:49 ` dpdklab
2024-06-27 20:50 ` dpdklab
2024-06-27 20:51 ` dpdklab
2024-06-27 21:05 ` |SUCCESS| " dpdklab
2024-06-27 21:21 ` |FAILURE| " dpdklab
2024-06-27 21:28 ` |SUCCESS| " dpdklab
2024-06-27 21:31 ` dpdklab
2024-06-27 21:32 ` |FAILURE| " dpdklab
2024-06-27 21:58 ` |SUCCESS| " dpdklab
2024-06-27 22:25 ` dpdklab
2024-06-27 22:46 ` dpdklab
2024-06-28  1:35 ` |FAILURE| " dpdklab
2024-06-28  1:36 ` dpdklab
2024-06-28  1:37 ` dpdklab
2024-06-28  1:40 ` dpdklab
2024-06-28  1:40 ` dpdklab
2024-06-28  1:42 ` dpdklab
2024-06-28  1:42 ` dpdklab
2024-06-28  1:43 ` dpdklab
2024-06-28  1:43 ` dpdklab
2024-06-28  1:43 ` dpdklab
2024-06-28  1:43 ` dpdklab
2024-06-28  1:44 ` dpdklab
2024-06-28  1:44 ` dpdklab
2024-06-28  1:45 ` dpdklab
2024-06-28  1:45 ` dpdklab
2024-06-28  1:46 ` dpdklab
2024-06-28  1:46 ` dpdklab
2024-06-28  1:46 ` dpdklab
2024-06-28  1:49 ` dpdklab
2024-06-28  1:50 ` dpdklab
2024-06-28  1:51 ` dpdklab
2024-06-28  1:52 ` dpdklab
2024-06-28  1:53 ` dpdklab
2024-06-28  1:54 ` dpdklab
2024-06-28  1:55 ` dpdklab
2024-06-28  1:56 ` dpdklab
2024-06-28  1:56 ` dpdklab
2024-06-28  1:57 ` dpdklab
2024-06-28  1:58 ` dpdklab
2024-06-28  1:58 ` dpdklab
2024-06-28  1:59 ` dpdklab
2024-06-28  1:59 ` dpdklab
2024-06-28  2:00 ` dpdklab
2024-06-28  2:01 ` dpdklab
2024-06-28  2:01 ` dpdklab
2024-06-28  2:28 ` dpdklab
2024-06-28  2:31 ` dpdklab
2024-06-28  2:33 ` dpdklab
2024-06-28  2:34 ` dpdklab
2024-06-28  2:34 ` dpdklab
2024-06-28  2:36 ` dpdklab
2024-06-28  2:37 ` dpdklab
2024-06-28  2:38 ` dpdklab
2024-06-28  2:38 ` dpdklab
2024-06-28  2:41 ` dpdklab
2024-06-28  2:41 ` dpdklab
2024-06-28  2:44 ` dpdklab
2024-06-28  2:44 ` dpdklab
2024-06-28  2:44 ` dpdklab
2024-06-28  2:45 ` dpdklab
2024-06-28  3:52 ` dpdklab
2024-06-28  3:53 ` dpdklab
2024-06-28  3:53 ` dpdklab
2024-06-28  3:54 ` dpdklab
2024-06-28  3:54 ` dpdklab
2024-06-28  3:55 ` dpdklab
2024-06-28  3:56 ` dpdklab
2024-06-28  3:56 ` dpdklab
2024-06-28  3:58 ` dpdklab
2024-06-28  3:59 ` dpdklab
2024-06-28  3:59 ` dpdklab
2024-06-28  4:00 ` dpdklab
2024-06-28  4:00 ` dpdklab
2024-06-28 13:47 ` dpdklab
2024-06-28 14:03 ` dpdklab
2024-06-29  2:57 ` |WARNING| " 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=667dc11a.050a0220.8e3ca.0e86SMTPIN_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).