From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137226-137232 [PATCH] [v3,7/7] net/mlx5: support modify
Date: Tue, 27 Feb 2024 18:55:41 -0800 (PST) [thread overview]
Message-ID: <65dea0ad.810a0220.7e8c8.fa70SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240226134556.2985054-8-michaelba@nvidia.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137232
_Functional Testing PASS_
Submitter: Michael Baum <michaelba@nvidia.com>
Date: Monday, February 26 2024 13:45:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:812898e35f0d21c18d5fae3261873661258abd83
137226-137232 --> 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/1
Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-82
Compiler: gcc 11.4.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/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29268/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-02-28 2:55 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240226134556.2985054-8-michaelba@nvidia.com>
2024-02-26 13:24 ` |SUCCESS| pw137226-137232 [PATCH v3 7/7] net/mlx5: support modify IPv6 flow label field qemudev
2024-02-26 13:29 ` qemudev
2024-02-26 13:48 ` |SUCCESS| pw137232 " checkpatch
2024-02-26 15:04 ` 0-day Robot
2024-02-28 2:47 ` |SUCCESS| pw137226-137232 [PATCH] [v3,7/7] net/mlx5: support modify dpdklab
2024-02-28 2:55 ` dpdklab [this message]
2024-02-28 2:57 ` dpdklab
2024-02-26 22:51 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-26 22:42 dpdklab
2024-02-26 22:03 dpdklab
2024-02-26 21:38 dpdklab
2024-02-26 21:28 dpdklab
2024-02-26 21:19 dpdklab
2024-02-26 19:54 dpdklab
2024-02-26 19:04 dpdklab
2024-02-26 19:04 dpdklab
2024-02-26 19:03 dpdklab
2024-02-26 19:02 dpdklab
2024-02-26 19:02 dpdklab
2024-02-26 19:00 dpdklab
2024-02-26 18:59 dpdklab
2024-02-26 18:59 dpdklab
2024-02-26 18:58 dpdklab
2024-02-26 18:58 dpdklab
2024-02-26 18:58 dpdklab
2024-02-26 18:57 dpdklab
2024-02-26 18:57 dpdklab
2024-02-26 18:55 dpdklab
2024-02-26 18:55 dpdklab
2024-02-26 18:55 dpdklab
2024-02-26 18:54 dpdklab
2024-02-26 18:54 dpdklab
2024-02-26 18:53 dpdklab
2024-02-26 18:52 dpdklab
2024-02-26 18:44 dpdklab
2024-02-26 18:41 dpdklab
2024-02-26 18:40 dpdklab
2024-02-26 18:40 dpdklab
2024-02-26 18:39 dpdklab
2024-02-26 18:37 dpdklab
2024-02-26 18:36 dpdklab
2024-02-26 18:36 dpdklab
2024-02-26 18:34 dpdklab
2024-02-26 18:34 dpdklab
2024-02-26 18:34 dpdklab
2024-02-26 18:34 dpdklab
2024-02-26 18:33 dpdklab
2024-02-26 18:32 dpdklab
2024-02-26 18:32 dpdklab
2024-02-26 18:32 dpdklab
2024-02-26 18:32 dpdklab
2024-02-26 18:32 dpdklab
2024-02-26 18:31 dpdklab
2024-02-26 18:31 dpdklab
2024-02-26 18:30 dpdklab
2024-02-26 18:26 dpdklab
2024-02-26 18:25 dpdklab
2024-02-26 18:25 dpdklab
2024-02-26 18:25 dpdklab
2024-02-26 18:25 dpdklab
2024-02-26 18:25 dpdklab
2024-02-26 18:24 dpdklab
2024-02-26 18:24 dpdklab
2024-02-26 18:24 dpdklab
2024-02-26 18:24 dpdklab
2024-02-26 18:24 dpdklab
2024-02-26 18:23 dpdklab
2024-02-26 18:23 dpdklab
2024-02-26 18:23 dpdklab
2024-02-26 18:23 dpdklab
2024-02-26 18:22 dpdklab
2024-02-26 18:22 dpdklab
2024-02-26 18:20 dpdklab
2024-02-26 18:19 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=65dea0ad.810a0220.7e8c8.fa70SMTPIN_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).