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| pw133939 [PATCH] net/mlx5: fix the validation of the sampl
Date: Tue, 07 Nov 2023 11:58:36 -0800 (PST)	[thread overview]
Message-ID: <654a96ec.020a0220.5e272.bcc3SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Jiawei Wang <jiaweiw@nvidia.com>
Date: Tuesday, November 07 2023 15:08:20 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:2bbad8f974e00552d106c27e1d157a31179ab5ec

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


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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-11-07 19:58 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 19:58 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-08  9:12 dpdklab
2023-11-08  4:57 dpdklab
2023-11-07 23:44 dpdklab
2023-11-07 23:36 dpdklab
2023-11-07 23:26 dpdklab
2023-11-07 23:14 dpdklab
2023-11-07 23:13 dpdklab
2023-11-07 23:08 dpdklab
2023-11-07 23:02 dpdklab
2023-11-07 23:00 dpdklab
2023-11-07 23:00 dpdklab
2023-11-07 23:00 dpdklab
2023-11-07 22:59 dpdklab
2023-11-07 22:59 dpdklab
2023-11-07 22:59 dpdklab
2023-11-07 22:58 dpdklab
2023-11-07 22:58 dpdklab
2023-11-07 22:58 dpdklab
2023-11-07 22:57 dpdklab
2023-11-07 22:57 dpdklab
2023-11-07 22:57 dpdklab
2023-11-07 22:46 dpdklab
2023-11-07 22:45 dpdklab
2023-11-07 22:45 dpdklab
2023-11-07 22:26 dpdklab
2023-11-07 22:20 dpdklab
2023-11-07 22:15 dpdklab
2023-11-07 22:15 dpdklab
2023-11-07 22:15 dpdklab
2023-11-07 22:15 dpdklab
2023-11-07 22:14 dpdklab
2023-11-07 22:13 dpdklab
2023-11-07 22:13 dpdklab
2023-11-07 22:12 dpdklab
2023-11-07 22:11 dpdklab
2023-11-07 22:00 dpdklab
2023-11-07 21:41 dpdklab
2023-11-07 21:41 dpdklab
2023-11-07 21:41 dpdklab
2023-11-07 21:40 dpdklab
2023-11-07 21:39 dpdklab
2023-11-07 21:37 dpdklab
2023-11-07 21:37 dpdklab
2023-11-07 21:37 dpdklab
2023-11-07 19:57 dpdklab
2023-11-07 19:51 dpdklab
2023-11-07 19:49 dpdklab
2023-11-07 19:43 dpdklab
2023-11-07 19:42 dpdklab
2023-11-07 19:42 dpdklab
2023-11-07 19:38 dpdklab
2023-11-07 19:38 dpdklab
2023-11-07 19:30 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=654a96ec.020a0220.5e272.bcc3SMTPIN_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).