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| pw135883 [PATCH] [v2] net/gve: enable imissed stats for GQ
Date: Tue, 16 Jan 2024 15:21:54 -0800 (PST)	[thread overview]
Message-ID: <65a70f92.810a0220.53d9e.6279SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Rushil Gupta <rushilg@google.com>
Date: Tuesday, January 16 2024 06:43:53 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:39a8b1251b204d3898b4c462184f60bda1b64698

135883 --> functional testing pass

Test environment and result as below:

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


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


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


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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-01-16 23:21 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 23:21 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-17 18:44 dpdklab
2024-01-17  4:39 dpdklab
2024-01-17  3:08 dpdklab
2024-01-17  3:03 dpdklab
2024-01-17  3:02 dpdklab
2024-01-17  2:51 dpdklab
2024-01-17  2:37 dpdklab
2024-01-17  2:37 dpdklab
2024-01-17  2:37 dpdklab
2024-01-17  2:37 dpdklab
2024-01-17  2:37 dpdklab
2024-01-17  2:36 dpdklab
2024-01-17  2:36 dpdklab
2024-01-17  2:36 dpdklab
2024-01-17  2:36 dpdklab
2024-01-17  2:36 dpdklab
2024-01-17  2:35 dpdklab
2024-01-17  2:35 dpdklab
2024-01-17  2:35 dpdklab
2024-01-17  2:35 dpdklab
2024-01-17  2:35 dpdklab
2024-01-17  2:32 dpdklab
2024-01-17  2:32 dpdklab
2024-01-17  2:32 dpdklab
2024-01-17  2:32 dpdklab
2024-01-17  2:32 dpdklab
2024-01-17  2:32 dpdklab
2024-01-17  2:31 dpdklab
2024-01-17  2:28 dpdklab
2024-01-17  2:27 dpdklab
2024-01-17  2:27 dpdklab
2024-01-17  2:27 dpdklab
2024-01-17  2:26 dpdklab
2024-01-17  2:26 dpdklab
2024-01-17  2:25 dpdklab
2024-01-17  2:24 dpdklab
2024-01-17  2:24 dpdklab
2024-01-17  2:21 dpdklab
2024-01-17  2:21 dpdklab
2024-01-17  2:21 dpdklab
2024-01-17  2:19 dpdklab
2024-01-17  2:17 dpdklab
2024-01-17  2:16 dpdklab
2024-01-17  2:15 dpdklab
2024-01-17  2:13 dpdklab
2024-01-17  1:36 dpdklab
2024-01-17  1:34 dpdklab
2024-01-17  1:34 dpdklab
2024-01-17  0:42 dpdklab
2024-01-16 23:50 dpdklab
2024-01-16 23:48 dpdklab
2024-01-16 23:30 dpdklab
2024-01-16 23:27 dpdklab
2024-01-16 23:26 dpdklab
2024-01-16 23:25 dpdklab
2024-01-16 23:23 dpdklab
2024-01-16 23:21 dpdklab
2024-01-16 23:17 dpdklab
2024-01-16 23:15 dpdklab
2024-01-16 23:15 dpdklab
2024-01-16 23:14 dpdklab
2024-01-16 22:49 dpdklab
2024-01-16 22:47 dpdklab
2024-01-16 22:46 dpdklab
2024-01-16 22:44 dpdklab
2024-01-16 22:42 dpdklab
2024-01-16 22:40 dpdklab
2024-01-16 22:13 dpdklab
2024-01-16 22:11 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=65a70f92.810a0220.53d9e.6279SMTPIN_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).