From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132721-132736 [PATCH] [v3,16/16] net/mlx5: fix METER_MAR
Date: Tue, 17 Oct 2023 14:42:14 -0700 (PDT) [thread overview]
Message-ID: <652effb6.630a0220.51efc.1adbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/132736
_Functional Testing PASS_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Tuesday, October 17 2023 08:09:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:55bc9233a2065b3003e90710e4d139159f7c3ebf
132721-132736 --> 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27961/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-17 21:42 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 21:42 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-18 17:38 dpdklab
2023-10-18 9:51 dpdklab
2023-10-18 6:08 dpdklab
2023-10-18 5:51 dpdklab
2023-10-18 5:30 dpdklab
2023-10-18 4:04 dpdklab
2023-10-18 3:54 dpdklab
2023-10-18 3:54 dpdklab
2023-10-18 3:48 dpdklab
2023-10-18 3:48 dpdklab
2023-10-18 3:47 dpdklab
2023-10-18 3:43 dpdklab
2023-10-18 3:42 dpdklab
2023-10-18 3:31 dpdklab
2023-10-18 3:31 dpdklab
2023-10-18 3:30 dpdklab
2023-10-18 3:29 dpdklab
2023-10-18 3:28 dpdklab
2023-10-18 3:28 dpdklab
2023-10-18 3:28 dpdklab
2023-10-18 3:25 dpdklab
2023-10-18 3:25 dpdklab
2023-10-18 3:24 dpdklab
2023-10-18 3:13 dpdklab
2023-10-18 3:12 dpdklab
2023-10-18 3:09 dpdklab
2023-10-18 3:09 dpdklab
2023-10-18 3:01 dpdklab
2023-10-18 3:00 dpdklab
2023-10-18 2:59 dpdklab
2023-10-18 2:57 dpdklab
2023-10-18 2:56 dpdklab
2023-10-18 2:56 dpdklab
2023-10-18 2:56 dpdklab
2023-10-18 2:55 dpdklab
2023-10-18 2:55 dpdklab
2023-10-18 2:54 dpdklab
2023-10-18 2:53 dpdklab
2023-10-18 2:46 dpdklab
2023-10-18 2:44 dpdklab
2023-10-18 2:44 dpdklab
2023-10-18 2:44 dpdklab
2023-10-18 2:00 dpdklab
2023-10-18 0:08 dpdklab
2023-10-17 23:52 dpdklab
2023-10-17 23:49 dpdklab
2023-10-17 23:47 dpdklab
2023-10-17 23:42 dpdklab
2023-10-17 21:39 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=652effb6.630a0220.51efc.1adbSMTPIN_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).