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| [GIT MASTER] 7ab964bebd0f5a0cc9d25b6679a8cf3d69ba8365
Date: Thu, 11 Jul 2024 17:19:12 -0700 (PDT)	[thread overview]
Message-ID: <66907680.050a0220.ee08d.de77SMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing pending_

Branch: dpdk

7ab964bebd0f5a0cc9d25b6679a8cf3d69ba8365 --> performance testing pending

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
Fail/Total: 0/1

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

Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 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/tarballs/29822/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-07-12  0:19 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-12  0:19 dpdklab [this message]
2024-07-12  0:29 dpdklab
2024-07-12  0:44 dpdklab
2024-07-12  0:48 dpdklab
2024-07-12  0:48 dpdklab
2024-07-12  0:49 dpdklab
2024-07-12  0:49 dpdklab
2024-07-12  0:52 dpdklab
2024-07-12  0:56 dpdklab
2024-07-12  0:56 dpdklab
2024-07-12  0:58 dpdklab
2024-07-12  0:59 dpdklab
2024-07-12  1:00 dpdklab
2024-07-12  1:00 dpdklab
2024-07-12  1:00 dpdklab
2024-07-12  1:01 dpdklab
2024-07-12  1:02 dpdklab
2024-07-12  1:02 dpdklab
2024-07-12  1:02 dpdklab
2024-07-12  1:03 dpdklab
2024-07-12  1:03 dpdklab
2024-07-12  1:07 dpdklab
2024-07-12  1:07 dpdklab
2024-07-12  1:08 dpdklab
2024-07-12  1:10 dpdklab
2024-07-12  1:11 dpdklab
2024-07-12  1:13 dpdklab
2024-07-12  1:15 dpdklab
2024-07-12  1:18 dpdklab
2024-07-12  1:19 dpdklab
2024-07-12  1:21 dpdklab
2024-07-12  1:23 dpdklab
2024-07-12  1:24 dpdklab
2024-07-12  1:35 dpdklab
2024-07-12  1:37 dpdklab
2024-07-12  1:38 dpdklab
2024-07-12  1:39 dpdklab
2024-07-12  1:42 dpdklab
2024-07-12  1:43 dpdklab
2024-07-12  1:44 dpdklab
2024-07-12  1:44 dpdklab
2024-07-12  1:48 dpdklab
2024-07-12  1:48 dpdklab
2024-07-12  1:52 dpdklab
2024-07-12  1:53 dpdklab
2024-07-12  1:56 dpdklab
2024-07-12  1:58 dpdklab
2024-07-12  2:01 dpdklab
2024-07-12  2:01 dpdklab
2024-07-12  2:01 dpdklab
2024-07-12  2:02 dpdklab
2024-07-12  2:03 dpdklab
2024-07-12  2:04 dpdklab
2024-07-12  2:04 dpdklab
2024-07-12  2:05 dpdklab
2024-07-12  2:05 dpdklab
2024-07-12  2:11 dpdklab
2024-07-12  2:13 dpdklab
2024-07-12  2:14 dpdklab
2024-07-12  2:14 dpdklab
2024-07-12  2:16 dpdklab
2024-07-12  2:17 dpdklab
2024-07-12  2:20 dpdklab
2024-07-12  2:21 dpdklab
2024-07-12  2:21 dpdklab
2024-07-12  2:21 dpdklab
2024-07-12  2:22 dpdklab
2024-07-12  2:23 dpdklab
2024-07-12  2:28 dpdklab
2024-07-12  2:33 dpdklab
2024-07-12  2:36 dpdklab
2024-07-12  2:37 dpdklab
2024-07-12  2:41 dpdklab
2024-07-12  2:42 dpdklab
2024-07-12  2:43 dpdklab
2024-07-12  2:44 dpdklab
2024-07-12  2:46 dpdklab
2024-07-12  2:47 dpdklab
2024-07-12  2:48 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=66907680.050a0220.ee08d.de77SMTPIN_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).