From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu
Subject: |SUCCESS| pw137200 [PATCH] net/mlx5: link status change for bonding
Date: Mon, 26 Feb 2024 11:53:46 -0800 (PST) [thread overview]
Message-ID: <65dcec4a.c80a0220.e7ea.78e4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137200
_Testing PASS_
Submitter: Haifei Luo <haifeil@nvidia.com>
Date: Monday, February 26 2024 12:03:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:260ed642fc7718d1a3058edef381f7aba06bbf44
137200 --> testing pass
Test environment and result as below:
+--------------+----------------------+----------------------+
| Environment | dpdk_fips_validation | compressdev_zlib_pmd |
+==============+======================+======================+
| Ubuntu 20.04 | PASS | SKIPPED |
+--------------+----------------------+----------------------+
| Ubuntu 22.04 | SKIPPED | PASS |
+--------------+----------------------+----------------------+
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 5.15.0-91-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29262/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-26 19:53 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 19:53 dpdklab [this message]
[not found] <20240226120341.175710-1-haifeil@nvidia.com>
2024-02-28 2:23 ` dpdklab
2024-02-28 2:26 ` dpdklab
2024-02-28 2:29 ` dpdklab
2024-02-28 2:31 ` dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-26 23:24 dpdklab
2024-02-26 23:15 dpdklab
2024-02-26 19:28 dpdklab
2024-02-26 19:04 dpdklab
2024-02-26 15:50 dpdklab
2024-02-26 15:43 dpdklab
2024-02-26 15:13 dpdklab
2024-02-26 15:11 dpdklab
2024-02-26 15:06 dpdklab
2024-02-26 15:03 dpdklab
2024-02-26 15:02 dpdklab
2024-02-26 15:01 dpdklab
2024-02-26 15:01 dpdklab
2024-02-26 14:58 dpdklab
2024-02-26 14:58 dpdklab
2024-02-26 14:57 dpdklab
2024-02-26 14:56 dpdklab
2024-02-26 14:54 dpdklab
2024-02-26 14:53 dpdklab
2024-02-26 14:52 dpdklab
2024-02-26 14:51 dpdklab
2024-02-26 14:50 dpdklab
2024-02-26 14:50 dpdklab
2024-02-26 14:46 dpdklab
2024-02-26 14:46 dpdklab
2024-02-26 14:45 dpdklab
2024-02-26 14:44 dpdklab
2024-02-26 14:43 dpdklab
2024-02-26 14:42 dpdklab
2024-02-26 14:42 dpdklab
2024-02-26 14:41 dpdklab
2024-02-26 14:41 dpdklab
2024-02-26 14:41 dpdklab
2024-02-26 14:40 dpdklab
2024-02-26 14:40 dpdklab
2024-02-26 14:39 dpdklab
2024-02-26 14:38 dpdklab
2024-02-26 14:37 dpdklab
2024-02-26 14:37 dpdklab
2024-02-26 14:36 dpdklab
2024-02-26 14:36 dpdklab
2024-02-26 14:35 dpdklab
2024-02-26 14:35 dpdklab
2024-02-26 14:34 dpdklab
2024-02-26 14:34 dpdklab
2024-02-26 14:34 dpdklab
2024-02-26 14:34 dpdklab
2024-02-26 14:33 dpdklab
2024-02-26 14:33 dpdklab
2024-02-26 14:33 dpdklab
2024-02-26 14:33 dpdklab
2024-02-26 14:33 dpdklab
2024-02-26 14:32 dpdklab
2024-02-26 14:32 dpdklab
2024-02-26 14:32 dpdklab
2024-02-26 14:32 dpdklab
2024-02-26 14:32 dpdklab
2024-02-26 14:32 dpdklab
2024-02-26 14:32 dpdklab
2024-02-26 14:30 dpdklab
2024-02-26 14:27 dpdklab
2024-02-26 14:27 dpdklab
2024-02-26 14:26 dpdklab
2024-02-26 14:25 dpdklab
2024-02-26 14:25 dpdklab
2024-02-26 14:12 dpdklab
2024-02-26 14:11 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=65dcec4a.c80a0220.e7ea.78e4SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@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).