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| pw137771-137793 [PATCH] [v5,23/23] net/cnxk: other flow op
Date: Fri, 01 Mar 2024 15:39:31 -0800 (PST)	[thread overview]
Message-ID: <65e26733.050a0220.68787.df2eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240301191451.57168-24-hkalra@marvell.com>

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

_Functional Testing PASS_

Submitter: Harman Kalra <hkalra@marvell.com>
Date: Friday, March 01 2024 19:14:50 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:ce8ce20ae46fe0df7632a0172c73d2dcd1ac0187

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


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

UNH-IOL DPDK Community Lab

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

  parent reply	other threads:[~2024-03-01 23:39 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240301191451.57168-24-hkalra@marvell.com>
2024-03-01 19:20 ` |WARNING| pw137793 [PATCH v5 23/23] net/cnxk: other flow operations checkpatch
2024-03-01 22:54 ` |SUCCESS| pw137771-137793 [PATCH] [v5,23/23] net/cnxk: other flow op dpdklab
2024-03-01 23:15 ` dpdklab
2024-03-01 23:21 ` dpdklab
2024-03-01 23:24 ` dpdklab
2024-03-01 23:25 ` dpdklab
2024-03-01 23:25 ` dpdklab
2024-03-01 23:25 ` dpdklab
2024-03-01 23:27 ` dpdklab
2024-03-01 23:29 ` dpdklab
2024-03-01 23:29 ` dpdklab
2024-03-01 23:35 ` dpdklab
2024-03-01 23:36 ` dpdklab
2024-03-01 23:37 ` dpdklab
2024-03-01 23:38 ` dpdklab
2024-03-01 23:39 ` dpdklab
2024-03-01 23:39 ` dpdklab [this message]
2024-03-01 23:41 ` dpdklab
2024-03-01 23:52 ` dpdklab
2024-03-02  0:12 ` dpdklab
2024-03-02  0:14 ` dpdklab
2024-03-02  0:37 ` dpdklab
2024-03-02  0:45 ` dpdklab
2024-03-02  2:17 ` dpdklab
2024-03-02  2:19 ` dpdklab
2024-03-02  2:26 ` dpdklab
2024-03-02  2:27 ` dpdklab
2024-03-02  2:28 ` dpdklab
2024-03-02  2:36 ` dpdklab
2024-03-02  2:37 ` dpdklab
2024-03-02  2:38 ` dpdklab
2024-03-02  2:39 ` dpdklab
2024-03-02  2:39 ` dpdklab
2024-03-02  2:40 ` dpdklab
2024-03-02  2:40 ` dpdklab
2024-03-02  2:41 ` dpdklab
2024-03-02  2:41 ` dpdklab
2024-03-02  2:42 ` dpdklab
2024-03-02  2:42 ` dpdklab
2024-03-02  2:43 ` dpdklab
2024-03-02  2:43 ` dpdklab
2024-03-02  2:43 ` dpdklab
2024-03-02  2:43 ` dpdklab
2024-03-02  2:43 ` dpdklab
2024-03-02  2:44 ` dpdklab
2024-03-02  2:45 ` dpdklab
2024-03-02  2:50 ` dpdklab
2024-03-02  2:51 ` dpdklab
2024-03-02  2:51 ` dpdklab
2024-03-02  2:51 ` dpdklab
2024-03-02  2:52 ` dpdklab
2024-03-02  2:53 ` dpdklab
2024-03-02  2:55 ` dpdklab
2024-03-02  2:57 ` dpdklab
2024-03-02  2:58 ` dpdklab
2024-03-02  3:00 ` dpdklab
2024-03-02  3:07 ` dpdklab
2024-03-02  3:10 ` dpdklab
2024-03-02  3:10 ` dpdklab
2024-03-02  3:38 ` dpdklab
2024-03-02  3:39 ` dpdklab
2024-03-02  3:40 ` dpdklab
2024-03-02  3:40 ` dpdklab
2024-03-02  3:41 ` dpdklab
2024-03-02  3:42 ` dpdklab
2024-03-02  3:42 ` dpdklab
2024-03-02  3:54 ` dpdklab
2024-03-02  3:56 ` dpdklab
2024-03-02  4:56 ` dpdklab
2024-03-02  5:12 ` dpdklab
2024-03-02  5:35 ` dpdklab
2024-03-03  3:21 ` dpdklab
2024-03-06  6:35 ` dpdklab
2024-03-06  7:45 ` dpdklab
2024-03-06  8:02 ` 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=65e26733.050a0220.68787.df2eSMTPIN_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).