From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw133383 [PATCH] net/mlx5: fix the workspace double free i
Date: Thu, 26 Oct 2023 02:56:30 -0700 (PDT) [thread overview]
Message-ID: <653a37ce.b00a0220.ed949.57f3SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/133383
_Testing PASS_
Submitter: Bing Zhao <bingz@nvidia.com>
Date: Thursday, October 26 2023 09:14:47
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2a0557d1ea21c3f63a212385348c97c414970e81
133383 --> testing pass
Test environment and result as below:
+-----------------+----------------+
| Environment | dpdk_unit_test |
+=================+================+
| CentOS Stream 9 | PASS |
+-----------------+----------------+
| CentOS Stream 8 | PASS |
+-----------------+----------------+
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28085/
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-26 9:56 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 9:56 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-28 1:12 dpdklab
2023-10-26 20:50 dpdklab
2023-10-26 20:46 dpdklab
2023-10-26 20:00 dpdklab
2023-10-26 19:53 dpdklab
2023-10-26 11:45 dpdklab
2023-10-26 10:39 dpdklab
2023-10-26 10:36 dpdklab
2023-10-26 10:36 dpdklab
2023-10-26 10:35 dpdklab
2023-10-26 10:28 dpdklab
2023-10-26 10:28 dpdklab
2023-10-26 10:28 dpdklab
2023-10-26 10:28 dpdklab
2023-10-26 10:23 dpdklab
2023-10-26 10:17 dpdklab
2023-10-26 10:16 dpdklab
2023-10-26 10:16 dpdklab
2023-10-26 10:15 dpdklab
2023-10-26 10:15 dpdklab
2023-10-26 10:15 dpdklab
2023-10-26 10:14 dpdklab
2023-10-26 10:14 dpdklab
2023-10-26 10:14 dpdklab
2023-10-26 10:14 dpdklab
2023-10-26 10:13 dpdklab
2023-10-26 10:01 dpdklab
2023-10-26 9:57 dpdklab
2023-10-26 9:56 dpdklab
2023-10-26 9:56 dpdklab
2023-10-26 9:56 dpdklab
2023-10-26 9:56 dpdklab
2023-10-26 9:56 dpdklab
2023-10-26 9:55 dpdklab
2023-10-26 9:55 dpdklab
2023-10-26 9:55 dpdklab
2023-10-26 9:55 dpdklab
2023-10-26 9:55 dpdklab
2023-10-26 9:55 dpdklab
2023-10-26 9:54 dpdklab
2023-10-26 9:54 dpdklab
2023-10-26 9:54 dpdklab
2023-10-26 9:51 dpdklab
2023-10-26 9:51 dpdklab
2023-10-26 9:50 dpdklab
2023-10-26 9:50 dpdklab
2023-10-26 9:50 dpdklab
2023-10-26 9:50 dpdklab
2023-10-26 9:50 dpdklab
2023-10-26 9:50 dpdklab
2023-10-26 9:49 dpdklab
2023-10-26 9:49 dpdklab
2023-10-26 9:48 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=653a37ce.b00a0220.ed949.57f3SMTPIN_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).