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| pw135176-135179 [PATCH] [4/4] net/mlx5: add modify field a
Date: Thu, 14 Dec 2023 15:38:09 -0800 (PST)	[thread overview]
Message-ID: <657b91e1.050a0220.50fff.5ce6SMTPIN_ADDED_MISSING@mx.google.com> (raw)

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

_Functional Testing PASS_

Submitter: Suanming Mou <suanmingm@nvidia.com>
Date: Thursday, December 14 2023 03:04:27 
DPDK git baseline: Repo:dpdk
  Branch: master
  CommitID:e5dc404d33ac1c6cea5c62a88489746c5cb5e35e

135176-135179 --> 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


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

UNH-IOL DPDK Community Lab

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

             reply	other threads:[~2023-12-14 23:38 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 23:38 dpdklab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-15 10:38 dpdklab
2023-12-15  3:12 dpdklab
2023-12-15  1:46 dpdklab
2023-12-15  1:26 dpdklab
2023-12-15  0:44 dpdklab
2023-12-15  0:31 dpdklab
2023-12-15  0:29 dpdklab
2023-12-15  0:29 dpdklab
2023-12-15  0:29 dpdklab
2023-12-15  0:29 dpdklab
2023-12-15  0:29 dpdklab
2023-12-15  0:27 dpdklab
2023-12-15  0:27 dpdklab
2023-12-15  0:27 dpdklab
2023-12-15  0:27 dpdklab
2023-12-15  0:25 dpdklab
2023-12-15  0:25 dpdklab
2023-12-15  0:24 dpdklab
2023-12-15  0:24 dpdklab
2023-12-15  0:22 dpdklab
2023-12-15  0:22 dpdklab
2023-12-15  0:22 dpdklab
2023-12-15  0:22 dpdklab
2023-12-15  0:21 dpdklab
2023-12-15  0:21 dpdklab
2023-12-15  0:21 dpdklab
2023-12-15  0:20 dpdklab
2023-12-15  0:12 dpdklab
2023-12-15  0:11 dpdklab
2023-12-15  0:11 dpdklab
2023-12-15  0:10 dpdklab
2023-12-15  0:10 dpdklab
2023-12-15  0:10 dpdklab
2023-12-15  0:08 dpdklab
2023-12-15  0:08 dpdklab
2023-12-15  0:07 dpdklab
2023-12-15  0:07 dpdklab
2023-12-15  0:06 dpdklab
2023-12-15  0:05 dpdklab
2023-12-15  0:05 dpdklab
2023-12-15  0:05 dpdklab
2023-12-15  0:04 dpdklab
2023-12-15  0:04 dpdklab
2023-12-15  0:03 dpdklab
2023-12-15  0:03 dpdklab
2023-12-15  0:02 dpdklab
2023-12-15  0:01 dpdklab
2023-12-15  0:01 dpdklab
2023-12-15  0:01 dpdklab
2023-12-15  0:00 dpdklab
2023-12-14 23:54 dpdklab
2023-12-14 23:53 dpdklab
2023-12-14 23:52 dpdklab
2023-12-14 23:52 dpdklab
2023-12-14 23:52 dpdklab
2023-12-14 23:51 dpdklab
2023-12-14 23:51 dpdklab
2023-12-14 23:51 dpdklab
2023-12-14 23:51 dpdklab
2023-12-14 23:50 dpdklab
2023-12-14 23:50 dpdklab
2023-12-14 23:50 dpdklab
2023-12-14 23:50 dpdklab
2023-12-14 23:38 dpdklab
2023-12-14 23:36 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=657b91e1.050a0220.50fff.5ce6SMTPIN_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).