From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142328 [PATCH] net/ice: fix possible memory leak
Date: Thu, 11 Jul 2024 14:52:07 -0700 (PDT) [thread overview]
Message-ID: <66905407.050a0220.172c.d133SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240711165907.3169191-1-vladimir.medvedkin@intel.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/142328
_Functional Testing PASS_
Submitter: Medvedkin, Vladimir <vladimir.medvedkin@intel.com>
Date: Thursday, July 11 2024 16:59:07
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e014773daacdb2f4be17061352592e5bb83a1d3f
142328 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 11.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| scatter | PASS |
+-----------------------------+--------+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| mtu_update | PASS |
+-----------------+--------+
| unit_tests_mbuf | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30499/
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-07-11 21:52 UTC|newest]
Thread overview: 121+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240711165907.3169191-1-vladimir.medvedkin@intel.com>
2024-07-11 16:38 ` qemudev
2024-07-11 16:42 ` qemudev
2024-07-11 16:59 ` |WARNING| " checkpatch
2024-07-11 20:43 ` |SUCCESS| " 0-day Robot
2024-07-11 21:27 ` dpdklab
2024-07-11 21:31 ` dpdklab
2024-07-11 21:31 ` dpdklab
2024-07-11 21:33 ` |PENDING| " dpdklab
2024-07-11 21:37 ` |SUCCESS| " dpdklab
2024-07-11 21:40 ` dpdklab
2024-07-11 21:42 ` dpdklab
2024-07-11 21:43 ` dpdklab
2024-07-11 21:44 ` dpdklab
2024-07-11 21:44 ` |PENDING| " dpdklab
2024-07-11 21:48 ` dpdklab
2024-07-11 21:48 ` dpdklab
2024-07-11 21:48 ` dpdklab
2024-07-11 21:49 ` dpdklab
2024-07-11 21:51 ` dpdklab
2024-07-11 21:52 ` dpdklab [this message]
2024-07-11 21:52 ` dpdklab
2024-07-11 21:53 ` dpdklab
2024-07-11 21:53 ` |SUCCESS| " dpdklab
2024-07-11 21:54 ` dpdklab
2024-07-11 21:55 ` |PENDING| " dpdklab
2024-07-11 21:57 ` |SUCCESS| " dpdklab
2024-07-11 21:59 ` dpdklab
2024-07-11 22:00 ` |PENDING| " dpdklab
2024-07-11 22:02 ` dpdklab
2024-07-11 22:05 ` dpdklab
2024-07-11 22:06 ` dpdklab
2024-07-11 22:07 ` dpdklab
2024-07-11 22:08 ` dpdklab
2024-07-11 22:08 ` dpdklab
2024-07-11 22:11 ` dpdklab
2024-07-11 22:11 ` dpdklab
2024-07-11 22:15 ` |SUCCESS| " dpdklab
2024-07-11 22:15 ` dpdklab
2024-07-11 22:15 ` |PENDING| " dpdklab
2024-07-11 22:18 ` dpdklab
2024-07-11 22:19 ` dpdklab
2024-07-11 22:23 ` dpdklab
2024-07-11 22:24 ` dpdklab
2024-07-11 22:24 ` dpdklab
2024-07-11 22:25 ` dpdklab
2024-07-11 22:25 ` dpdklab
2024-07-11 22:25 ` dpdklab
2024-07-11 22:26 ` dpdklab
2024-07-11 22:27 ` dpdklab
2024-07-11 22:29 ` |SUCCESS| " dpdklab
2024-07-11 22:30 ` |PENDING| " dpdklab
2024-07-11 22:44 ` dpdklab
2024-07-11 22:44 ` dpdklab
2024-07-11 22:45 ` dpdklab
2024-07-11 22:46 ` dpdklab
2024-07-11 22:48 ` dpdklab
2024-07-11 22:50 ` dpdklab
2024-07-11 22:50 ` dpdklab
2024-07-11 22:50 ` dpdklab
2024-07-11 22:51 ` dpdklab
2024-07-11 22:52 ` dpdklab
2024-07-11 22:53 ` dpdklab
2024-07-11 22:53 ` dpdklab
2024-07-11 22:54 ` dpdklab
2024-07-11 22:55 ` dpdklab
2024-07-11 22:56 ` dpdklab
2024-07-11 22:56 ` dpdklab
2024-07-11 22:57 ` dpdklab
2024-07-11 22:58 ` dpdklab
2024-07-11 23:00 ` dpdklab
2024-07-11 23:00 ` dpdklab
2024-07-11 23:02 ` dpdklab
2024-07-11 23:05 ` |SUCCESS| " dpdklab
2024-07-11 23:07 ` |PENDING| " dpdklab
2024-07-11 23:08 ` dpdklab
2024-07-11 23:13 ` dpdklab
2024-07-11 23:17 ` dpdklab
2024-07-11 23:21 ` dpdklab
2024-07-11 23:27 ` |SUCCESS| " dpdklab
2024-07-11 23:29 ` |PENDING| " dpdklab
2024-07-11 23:33 ` dpdklab
2024-07-11 23:34 ` dpdklab
2024-07-11 23:34 ` dpdklab
2024-07-11 23:37 ` dpdklab
2024-07-11 23:41 ` dpdklab
2024-07-11 23:43 ` dpdklab
2024-07-11 23:44 ` dpdklab
2024-07-11 23:45 ` dpdklab
2024-07-11 23:54 ` dpdklab
2024-07-11 23:56 ` dpdklab
2024-07-11 23:57 ` dpdklab
2024-07-11 23:58 ` dpdklab
2024-07-11 23:58 ` dpdklab
2024-07-11 23:59 ` dpdklab
2024-07-12 0:02 ` dpdklab
2024-07-12 0:04 ` dpdklab
2024-07-12 0:07 ` dpdklab
2024-07-12 0:08 ` dpdklab
2024-07-12 0:09 ` dpdklab
2024-07-12 0:11 ` dpdklab
2024-07-12 0:11 ` dpdklab
2024-07-12 0:11 ` dpdklab
2024-07-12 0:11 ` dpdklab
2024-07-12 0:12 ` dpdklab
2024-07-12 0:16 ` |SUCCESS| " dpdklab
2024-07-12 0:16 ` |PENDING| " dpdklab
2024-07-12 0:17 ` dpdklab
2024-07-12 0:19 ` dpdklab
2024-07-12 0:20 ` dpdklab
2024-07-12 0:21 ` dpdklab
2024-07-12 0:22 ` dpdklab
2024-07-12 0:29 ` dpdklab
2024-07-12 0:31 ` dpdklab
2024-07-12 0:34 ` |SUCCESS| " dpdklab
2024-07-12 1:07 ` dpdklab
2024-07-12 4:34 ` dpdklab
2024-07-13 0:07 ` dpdklab
2024-07-14 6:21 ` dpdklab
2024-07-14 12:46 ` dpdklab
2024-07-14 20:49 ` dpdklab
2024-07-14 20:56 ` 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=66905407.050a0220.172c.d133SMTPIN_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).