From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw121532 [PATCH] [v3] malloc: enhance NUMA affinity heuristic
Date: Tue, 3 Jan 2023 09:00:21 -0500 (EST) [thread overview]
Message-ID: <20230103140021.3D35310618C@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 807 bytes --]
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/121532
_Functional Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Tuesday, January 03 2023 13:32:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:373f4c7de8ff350548cacc3d56e788461677f2c7
121532 --> 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/24866/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-01-03 14:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 14:00 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-04 2:24 dpdklab
2023-01-04 1:15 dpdklab
2023-01-04 0:11 dpdklab
2023-01-03 22:54 dpdklab
2023-01-03 22:37 dpdklab
2023-01-03 22:33 dpdklab
2023-01-03 22:22 dpdklab
2023-01-03 22:05 dpdklab
2023-01-03 21:59 dpdklab
2023-01-03 21:52 dpdklab
2023-01-03 17:27 dpdklab
2023-01-03 14:54 dpdklab
2023-01-03 14:34 dpdklab
2023-01-03 14:21 dpdklab
2023-01-03 14:14 dpdklab
2023-01-03 14:04 dpdklab
[not found] <20230103133216.961495-1-david.marchand@redhat.com>
2023-01-03 13:24 ` |SUCCESS| pw121532 [PATCH v3] " qemudev
2023-01-03 13:28 ` qemudev
2023-01-03 13:33 ` checkpatch
2023-01-03 14:19 ` 0-day Robot
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=20230103140021.3D35310618C@noxus.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).