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] e96b7d0eae4b5450f2b12bb2377b8755ad882f90
Date: Mon, 15 Jul 2024 08:09:22 -0700 (PDT)	[thread overview]
Message-ID: <66953ba2.050a0220.e39e5.e3beSMTPIN_ADDED_MISSING@mx.google.com> (raw)

_Performance Testing pending_

Branch: 23.11-staging

e96b7d0eae4b5450f2b12bb2377b8755ad882f90 --> performance testing pending

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 XL710-QDA2 40000 Mbps
Fail/Total: 0/1

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

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/1

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

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/tarballs/29645/

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-07-15 15:09 UTC|newest]

Thread overview: 120+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15 15:09 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-07-17  1:37 dpdklab
2024-07-16 17:19 dpdklab
2024-07-16 17:02 dpdklab
2024-07-16 16:46 dpdklab
2024-07-16 16:43 dpdklab
2024-07-16 16:23 dpdklab
2024-07-16  9:03 dpdklab
2024-07-15 20:30 dpdklab
2024-07-15 20:27 dpdklab
2024-07-15 20:26 dpdklab
2024-07-15 20:23 dpdklab
2024-07-15 20:21 dpdklab
2024-07-15 20:20 dpdklab
2024-07-15 20:20 dpdklab
2024-07-15 20:19 dpdklab
2024-07-15 20:19 dpdklab
2024-07-15 20:18 dpdklab
2024-07-15 20:13 dpdklab
2024-07-15 20:11 dpdklab
2024-07-15 20:10 dpdklab
2024-07-15 20:06 dpdklab
2024-07-15 20:05 dpdklab
2024-07-15 20:01 dpdklab
2024-07-15 20:00 dpdklab
2024-07-15 20:00 dpdklab
2024-07-15 19:59 dpdklab
2024-07-15 19:50 dpdklab
2024-07-15 19:46 dpdklab
2024-07-15 19:43 dpdklab
2024-07-15 19:39 dpdklab
2024-07-15 19:34 dpdklab
2024-07-15 19:07 dpdklab
2024-07-15 19:07 dpdklab
2024-07-15 19:07 dpdklab
2024-07-15 19:06 dpdklab
2024-07-15 19:04 dpdklab
2024-07-15 19:03 dpdklab
2024-07-15 18:59 dpdklab
2024-07-15 18:49 dpdklab
2024-07-15 18:46 dpdklab
2024-07-15 18:41 dpdklab
2024-07-15 18:38 dpdklab
2024-07-15 18:29 dpdklab
2024-07-15 18:22 dpdklab
2024-07-15 18:19 dpdklab
2024-07-15 18:14 dpdklab
2024-07-15 18:05 dpdklab
2024-07-15 18:00 dpdklab
2024-07-15 17:52 dpdklab
2024-07-15 17:51 dpdklab
2024-07-15 17:50 dpdklab
2024-07-15 17:30 dpdklab
2024-07-15 17:30 dpdklab
2024-07-15 17:26 dpdklab
2024-07-15 17:23 dpdklab
2024-07-15 17:21 dpdklab
2024-07-15 17:16 dpdklab
2024-07-15 15:54 dpdklab
2024-07-15 15:20 dpdklab
2024-07-15 15:11 dpdklab
2024-07-15 15:02 dpdklab
2024-07-15  0:11 dpdklab
2024-07-10 22:01 dpdklab
2024-07-10 21:36 dpdklab
2024-07-10 21:15 dpdklab
2024-07-10 21:12 dpdklab
2024-07-10 21:11 dpdklab
2024-07-10 21:10 dpdklab
2024-06-29 19:44 dpdklab
2024-06-29 19:37 dpdklab
2024-06-29 19:30 dpdklab
2024-06-29 19:17 dpdklab
2024-06-29 19:02 dpdklab
2024-06-29 18:55 dpdklab
2024-06-29 18:32 dpdklab
2024-06-29 18:28 dpdklab
2024-06-29 18:07 dpdklab
2024-06-29 18:04 dpdklab
2024-06-29 18:01 dpdklab
2024-06-29 17:57 dpdklab
2024-06-29 17:55 dpdklab
2024-06-29 17:54 dpdklab
2024-06-29 17:53 dpdklab
2024-06-29 17:46 dpdklab
2024-06-29 17:35 dpdklab
2024-06-29 17:34 dpdklab
2024-06-29 17:19 dpdklab
2024-06-29 17:15 dpdklab
2024-06-29 16:54 dpdklab
2024-06-29 16:49 dpdklab
2024-06-29 16:47 dpdklab
2024-06-29 16:43 dpdklab
2024-06-29 16:40 dpdklab
2024-06-29 16:38 dpdklab
2024-06-29 16:37 dpdklab
2024-06-29 16:24 dpdklab
2024-06-29 16:23 dpdklab
2024-06-29 16:20 dpdklab
2024-06-29 16:20 dpdklab
2024-06-29 16:11 dpdklab
2024-06-29 16:11 dpdklab
2024-06-29 16:10 dpdklab
2024-06-29 16:09 dpdklab
2024-06-29 16:09 dpdklab
2024-06-29 16:06 dpdklab
2024-06-29 16:01 dpdklab
2024-06-29 16:00 dpdklab
2024-06-29 15:59 dpdklab
2024-06-29 15:53 dpdklab
2024-06-29 15:50 dpdklab
2024-06-29 15:49 dpdklab
2024-06-29 15:49 dpdklab
2024-06-29 15:47 dpdklab
2024-06-29 15:45 dpdklab
2024-06-29 15:44 dpdklab
2024-06-29 15:41 dpdklab
2024-06-29 15:32 dpdklab
2024-06-29 15:19 dpdklab
2024-06-29 15:14 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=66953ba2.050a0220.e39e5.e3beSMTPIN_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).