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| pw137109 [PATCH] [1/1] net/octeon_ep: use devarg to enable
Date: Fri, 23 Feb 2024 14:00:34 -0800 (PST)	[thread overview]
Message-ID: <65d91582.050a0220.4cfa0.011bSMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Vamsi Attunuru <vattunuru@marvell.com>
Date: Friday, February 23 2024 15:39:38 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e9c81b801b647b1e06bb9f0e6da99b49b28b5162

137109 --> 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 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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2024-02-23 22:00 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-23 22:00 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-02-24  6:42 dpdklab
2024-02-24  6:02 dpdklab
2024-02-24  5:38 dpdklab
2024-02-24  0:32 dpdklab
2024-02-24  0:30 dpdklab
2024-02-24  0:27 dpdklab
2024-02-24  0:01 dpdklab
2024-02-23 23:55 dpdklab
2024-02-23 23:49 dpdklab
2024-02-23 23:48 dpdklab
2024-02-23 23:42 dpdklab
2024-02-23 23:41 dpdklab
2024-02-23 23:40 dpdklab
2024-02-23 23:32 dpdklab
2024-02-23 23:24 dpdklab
2024-02-23 23:20 dpdklab
2024-02-23 23:19 dpdklab
2024-02-23 23:01 dpdklab
2024-02-23 22:56 dpdklab
2024-02-23 22:56 dpdklab
2024-02-23 22:55 dpdklab
2024-02-23 22:54 dpdklab
2024-02-23 22:54 dpdklab
2024-02-23 22:47 dpdklab
2024-02-23 22:47 dpdklab
2024-02-23 22:46 dpdklab
2024-02-23 22:46 dpdklab
2024-02-23 22:45 dpdklab
2024-02-23 22:44 dpdklab
2024-02-23 22:43 dpdklab
2024-02-23 22:43 dpdklab
2024-02-23 22:42 dpdklab
2024-02-23 22:42 dpdklab
2024-02-23 22:31 dpdklab
2024-02-23 22:31 dpdklab
2024-02-23 22:30 dpdklab
2024-02-23 22:29 dpdklab
2024-02-23 22:29 dpdklab
2024-02-23 22:28 dpdklab
2024-02-23 22:28 dpdklab
2024-02-23 22:28 dpdklab
2024-02-23 22:27 dpdklab
2024-02-23 22:26 dpdklab
2024-02-23 22:25 dpdklab
2024-02-23 21:44 dpdklab
2024-02-23 21:43 dpdklab
2024-02-23 21:43 dpdklab
2024-02-23 21:38 dpdklab
2024-02-23 21:36 dpdklab
2024-02-23 21:35 dpdklab
2024-02-23 21:32 dpdklab
2024-02-23 21:31 dpdklab
2024-02-23 21:30 dpdklab
2024-02-23 21:30 dpdklab
2024-02-23 21:27 dpdklab
2024-02-23 21:26 dpdklab
2024-02-23 21:26 dpdklab
2024-02-23 21:25 dpdklab
2024-02-23 21:25 dpdklab
2024-02-23 21:24 dpdklab
2024-02-23 21:24 dpdklab
2024-02-23 21:24 dpdklab
2024-02-23 21:24 dpdklab
2024-02-23 21:23 dpdklab
2024-02-23 21:23 dpdklab
2024-02-23 21:22 dpdklab
2024-02-23 21:22 dpdklab
2024-02-23 21:21 dpdklab
2024-02-23 21: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=65d91582.050a0220.4cfa0.011bSMTPIN_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).