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| pw135324 [PATCH] net/gve: Enable stats reporting for GQ fo
Date: Mon, 18 Dec 2023 21:06:16 -0800 (PST)	[thread overview]
Message-ID: <658124c8.5d0a0220.86433.7a49SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/135324

_Functional Testing PASS_

Submitter: Rushil Gupta <rushilg@google.com>
Date: Tuesday, December 19 2023 02:16:50 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e

135324 --> functional testing pass

Test environment and result as below:

Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4


Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4


Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-19  5:06 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  5:06 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-19 16:39 dpdklab
2023-12-19 16:30 dpdklab
2023-12-19 16:24 dpdklab
2023-12-19 16:09 dpdklab
2023-12-19 16:03 dpdklab
2023-12-19  7:39 dpdklab
2023-12-19  5:39 dpdklab
2023-12-19  5:32 dpdklab
2023-12-19  5:31 dpdklab
2023-12-19  5:22 dpdklab
2023-12-19  5:20 dpdklab
2023-12-19  5:20 dpdklab
2023-12-19  5:19 dpdklab
2023-12-19  5:12 dpdklab
2023-12-19  5:12 dpdklab
2023-12-19  5:12 dpdklab
2023-12-19  5:11 dpdklab
2023-12-19  5:10 dpdklab
2023-12-19  5:10 dpdklab
2023-12-19  5:10 dpdklab
2023-12-19  5:09 dpdklab
2023-12-19  5:09 dpdklab
2023-12-19  5:08 dpdklab
2023-12-19  5:08 dpdklab
2023-12-19  5:08 dpdklab
2023-12-19  5:08 dpdklab
2023-12-19  5:08 dpdklab
2023-12-19  5:08 dpdklab
2023-12-19  5:07 dpdklab
2023-12-19  5:07 dpdklab
2023-12-19  5:06 dpdklab
2023-12-19  5:06 dpdklab
2023-12-19  5:06 dpdklab
2023-12-19  5:06 dpdklab
2023-12-19  5:05 dpdklab
2023-12-19  5:05 dpdklab
2023-12-19  5:05 dpdklab
2023-12-19  5:05 dpdklab
2023-12-19  5:05 dpdklab
2023-12-19  5:05 dpdklab
2023-12-19  5:04 dpdklab
2023-12-19  5:03 dpdklab
2023-12-19  5:02 dpdklab
2023-12-19  5:02 dpdklab
2023-12-19  5:02 dpdklab
2023-12-19  5:02 dpdklab
2023-12-19  5:01 dpdklab
2023-12-19  5:00 dpdklab
2023-12-19  5:00 dpdklab
2023-12-19  4:59 dpdklab
2023-12-19  4:59 dpdklab
2023-12-19  4:59 dpdklab
2023-12-19  4:59 dpdklab
2023-12-19  4:59 dpdklab
2023-12-19  4:59 dpdklab
2023-12-19  4:58 dpdklab
2023-12-19  4:58 dpdklab
2023-12-19  4:58 dpdklab
2023-12-19  4:55 dpdklab
2023-12-19  4:54 dpdklab
2023-12-19  4:52 dpdklab
2023-12-19  4:52 dpdklab
2023-12-19  4:51 dpdklab
2023-12-19  4:51 dpdklab
2023-12-19  4:50 dpdklab
2023-12-19  4:49 dpdklab
2023-12-19  4:47 dpdklab
2023-12-19  4:47 dpdklab
2023-12-19  4:46 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=658124c8.5d0a0220.86433.7a49SMTPIN_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).