From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138082-138085 [PATCH] [v2,5/5] eal: fix memzone fbarray
Date: Thu, 07 Mar 2024 19:31:36 -0800 (PST) [thread overview]
Message-ID: <65ea8698.050a0220.a4666.2645SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240307070113.29580-6-artemyko@nvidia.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138085
_Functional Testing PASS_
Submitter: Artemy Kovalyov <artemyko@nvidia.com>
Date: Thursday, March 07 2024 07:01:13
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2a454f84f715608ee709a4c6ba00edf2e4b62b69
138082-138085 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29452/
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-03-08 3:31 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240307070113.29580-6-artemyko@nvidia.com>
2024-03-07 6:40 ` |SUCCESS| pw138082-138085 [PATCH v2 5/5] eal: fix memzone fbarray cleanup qemudev
2024-03-07 6:44 ` qemudev
2024-03-07 7:02 ` |WARNING| pw138085 " checkpatch
2024-03-07 8:04 ` |SUCCESS| " 0-day Robot
2024-03-07 8:10 ` |SUCCESS| pw138082-138085 [PATCH] [v2,5/5] eal: fix memzone fbarray dpdklab
2024-03-07 8:10 ` dpdklab
2024-03-07 8:12 ` dpdklab
2024-03-07 8:17 ` dpdklab
2024-03-07 8:35 ` dpdklab
2024-03-07 8:40 ` dpdklab
2024-03-07 8:41 ` dpdklab
2024-03-07 8:45 ` dpdklab
2024-03-07 8:45 ` dpdklab
2024-03-07 8:45 ` dpdklab
2024-03-07 8:49 ` dpdklab
2024-03-07 8:49 ` dpdklab
2024-03-07 8:52 ` dpdklab
2024-03-07 8:59 ` dpdklab
2024-03-07 9:00 ` dpdklab
2024-03-07 9:05 ` dpdklab
2024-03-07 9:06 ` dpdklab
2024-03-07 9:19 ` dpdklab
2024-03-07 9:24 ` dpdklab
2024-03-07 9:27 ` dpdklab
2024-03-07 9:28 ` dpdklab
2024-03-07 9:29 ` dpdklab
2024-03-07 9:35 ` dpdklab
2024-03-07 9:37 ` dpdklab
2024-03-07 9:40 ` dpdklab
2024-03-07 9:56 ` dpdklab
2024-03-07 10:03 ` dpdklab
2024-03-07 10:07 ` dpdklab
2024-03-07 10:08 ` dpdklab
2024-03-07 10:08 ` dpdklab
2024-03-07 10:12 ` dpdklab
2024-03-07 10:12 ` dpdklab
2024-03-07 10:12 ` dpdklab
2024-03-07 10:13 ` dpdklab
2024-03-07 10:13 ` dpdklab
2024-03-07 10:13 ` dpdklab
2024-03-07 10:13 ` dpdklab
2024-03-07 10:14 ` dpdklab
2024-03-07 10:15 ` dpdklab
2024-03-07 10:15 ` dpdklab
2024-03-07 10:15 ` dpdklab
2024-03-07 10:15 ` dpdklab
2024-03-07 10:15 ` dpdklab
2024-03-07 10:16 ` dpdklab
2024-03-07 10:16 ` dpdklab
2024-03-07 10:17 ` dpdklab
2024-03-07 10:17 ` dpdklab
2024-03-07 10:22 ` dpdklab
2024-03-07 10:22 ` dpdklab
2024-03-07 10:23 ` dpdklab
2024-03-07 10:23 ` dpdklab
2024-03-07 10:24 ` dpdklab
2024-03-07 10:24 ` dpdklab
2024-03-07 10:24 ` dpdklab
2024-03-07 10:29 ` dpdklab
2024-03-07 10:29 ` dpdklab
2024-03-07 10:34 ` dpdklab
2024-03-07 10:41 ` dpdklab
2024-03-07 10:45 ` dpdklab
2024-03-07 10:48 ` dpdklab
2024-03-07 11:05 ` dpdklab
2024-03-07 13:21 ` dpdklab
2024-03-08 3:19 ` dpdklab
2024-03-08 3:23 ` dpdklab
2024-03-08 3:27 ` dpdklab
2024-03-08 3:31 ` dpdklab [this message]
2024-03-11 10:10 ` dpdklab
2024-03-11 10:46 ` 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=65ea8698.050a0220.a4666.2645SMTPIN_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).