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| pw128518-128521 [PATCH] [4/4] net/mlx5: implement Flow upd
Date: Mon, 12 Jun 2023 20:46:35 -0700 (PDT)	[thread overview]
Message-ID: <6487e69b.b00a0220.bf662.8200SMTPIN_ADDED_MISSING@mx.google.com> (raw)

Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/128521

_Functional Testing PASS_

Submitter: Alexander Kozyrev <akozyrev@nvidia.com>
Date: Monday, June 12 2023 20:05:52 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:b6c419dde10e9f5dec7a02098c48060a7493420c

128518-128521 --> functional testing pass

Test environment and result as below:

Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2


Ubuntu 20.04 ARM
Kernel: 5.11.0-46-generic
Compiler: gcc 9.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-148-generic aarch64
Compiler: gcc 9.4
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-06-13  3:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13  3:46 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-06-13  4:05 dpdklab
2023-06-13  3:17 dpdklab
2023-06-13  3:13 dpdklab
2023-06-13  3:12 dpdklab
2023-06-13  3:01 dpdklab
2023-06-13  2:33 dpdklab
2023-06-13  1:48 dpdklab
2023-06-13  1:47 dpdklab
2023-06-13  1:28 dpdklab
2023-06-13  1:21 dpdklab
2023-06-13  1:17 dpdklab
2023-06-13  1:12 dpdklab
2023-06-13  1:07 dpdklab
2023-06-13  1:07 dpdklab
2023-06-13  1:07 dpdklab
2023-06-13  1:01 dpdklab
2023-06-13  1:01 dpdklab
2023-06-13  1:01 dpdklab
2023-06-13  0:58 dpdklab
2023-06-13  0:55 dpdklab
2023-06-13  0:42 dpdklab
2023-06-13  0:38 dpdklab
2023-06-13  0:38 dpdklab
2023-06-13  0:34 dpdklab
2023-06-13  0:34 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=6487e69b.b00a0220.bf662.8200SMTPIN_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).