From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138088 [PATCH] net/mlx5: fix age position in hairpin spl
Date: Mon, 11 Mar 2024 07:11:52 -0700 (PDT) [thread overview]
Message-ID: <65ef1128.050a0220.748c9.3ff4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240307080924.310710-1-bingz@nvidia.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138088
_Testing PASS_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Thursday, March 07 2024 08:09:24
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6666628362c94a0b567a39a0177539c12c97d999
138088 --> 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/29454/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2024-03-11 14:11 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240307080924.310710-1-bingz@nvidia.com>
2024-03-07 7:52 ` |SUCCESS| pw138088 [PATCH] net/mlx5: fix age position in hairpin split qemudev
2024-03-07 7:57 ` qemudev
2024-03-07 8:11 ` |WARNING| " checkpatch
2024-03-07 9:04 ` |SUCCESS| " 0-day Robot
2024-03-07 10:29 ` |SUCCESS| pw138088 [PATCH] net/mlx5: fix age position in hairpin spl dpdklab
2024-03-07 10:30 ` dpdklab
2024-03-07 10:31 ` dpdklab
2024-03-07 10:32 ` dpdklab
2024-03-07 10:34 ` dpdklab
2024-03-07 10:35 ` dpdklab
2024-03-07 10:35 ` dpdklab
2024-03-07 10:35 ` dpdklab
2024-03-07 10:50 ` dpdklab
2024-03-07 10:51 ` dpdklab
2024-03-07 10:56 ` dpdklab
2024-03-07 11:06 ` dpdklab
2024-03-07 11:07 ` dpdklab
2024-03-07 11:08 ` dpdklab
2024-03-07 11:09 ` dpdklab
2024-03-07 11:09 ` dpdklab
2024-03-07 11:10 ` dpdklab
2024-03-07 11:10 ` dpdklab
2024-03-07 11:11 ` dpdklab
2024-03-07 11:11 ` dpdklab
2024-03-07 11:12 ` dpdklab
2024-03-07 11:13 ` dpdklab
2024-03-07 11:13 ` dpdklab
2024-03-07 11:20 ` dpdklab
2024-03-07 11:20 ` dpdklab
2024-03-07 11:21 ` dpdklab
2024-03-07 11:21 ` dpdklab
2024-03-07 11:26 ` dpdklab
2024-03-07 11:27 ` dpdklab
2024-03-07 11:28 ` dpdklab
2024-03-07 11:28 ` dpdklab
2024-03-07 11:29 ` dpdklab
2024-03-07 11:29 ` dpdklab
2024-03-07 11:29 ` dpdklab
2024-03-07 11:30 ` dpdklab
2024-03-07 11:30 ` dpdklab
2024-03-07 11:31 ` dpdklab
2024-03-07 11:32 ` dpdklab
2024-03-07 11:42 ` dpdklab
2024-03-07 11:43 ` dpdklab
2024-03-07 11:45 ` dpdklab
2024-03-07 11:46 ` dpdklab
2024-03-07 11:47 ` dpdklab
2024-03-07 11:48 ` dpdklab
2024-03-07 11:49 ` dpdklab
2024-03-07 11:50 ` dpdklab
2024-03-07 11:50 ` dpdklab
2024-03-07 11:51 ` dpdklab
2024-03-07 11:51 ` dpdklab
2024-03-07 11:51 ` dpdklab
2024-03-07 11:52 ` dpdklab
2024-03-07 11:53 ` dpdklab
2024-03-07 11:53 ` dpdklab
2024-03-07 11:54 ` dpdklab
2024-03-07 11:56 ` dpdklab
2024-03-07 11:56 ` dpdklab
2024-03-07 11:57 ` dpdklab
2024-03-07 11:57 ` dpdklab
2024-03-07 12:05 ` dpdklab
2024-03-07 12:09 ` dpdklab
2024-03-07 12:13 ` dpdklab
2024-03-07 12:15 ` |FAILURE| " dpdklab
2024-03-07 13:02 ` |SUCCESS| " dpdklab
2024-03-07 18:02 ` dpdklab
2024-03-08 4:01 ` dpdklab
2024-03-08 4:05 ` dpdklab
2024-03-08 4:09 ` dpdklab
2024-03-08 4:13 ` dpdklab
2024-03-11 12:40 ` dpdklab
2024-03-11 14:11 ` dpdklab [this message]
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=65ef1128.050a0220.748c9.3ff4SMTPIN_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).