From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131146 [PATCH] mempool: add cache guard to per-lcore deb
Date: Mon, 04 Sep 2023 02:41:38 -0700 (PDT) [thread overview]
Message-ID: <64f5a652.c80a0220.78ba8.0580SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/131146
_Functional Testing PASS_
Submitter: Morten Brorup <mb@smartsharesystems.com>
Date: Monday, September 04 2023 09:10:20
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:799d56f1192d72872e63fbb3d2c7f776b7ae89b0
131146 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27517/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-04 9:41 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 9:41 dpdklab [this message]
2023-09-04 9:41 dpdklab
2023-09-04 9:42 dpdklab
2023-09-04 9:44 dpdklab
2023-09-04 9:47 dpdklab
2023-09-04 9:48 dpdklab
2023-09-04 9:51 dpdklab
2023-09-04 9:52 dpdklab
2023-09-04 9:54 dpdklab
2023-09-04 9:54 dpdklab
2023-09-04 9:54 dpdklab
2023-09-04 9:58 dpdklab
2023-09-04 9:59 dpdklab
2023-09-04 10:00 dpdklab
2023-09-04 10:01 dpdklab
2023-09-04 10:03 dpdklab
2023-09-04 10:03 dpdklab
2023-09-04 10:03 dpdklab
2023-09-04 10:03 dpdklab
2023-09-04 10:04 dpdklab
2023-09-04 10:08 dpdklab
2023-09-04 10:10 dpdklab
2023-09-04 10:13 dpdklab
2023-09-04 10:13 dpdklab
2023-09-04 10:14 dpdklab
2023-09-04 10:15 dpdklab
2023-09-04 10:19 dpdklab
2023-09-04 10:21 dpdklab
2023-09-04 10:23 dpdklab
2023-09-04 10:25 dpdklab
2023-09-04 10:25 dpdklab
2023-09-04 10:26 dpdklab
2023-09-04 10:28 dpdklab
2023-09-04 10:29 dpdklab
2023-09-04 10:30 dpdklab
2023-09-04 10:31 dpdklab
2023-09-04 10:42 dpdklab
2023-09-04 10:45 dpdklab
2023-09-04 11:07 dpdklab
2023-09-04 11:15 dpdklab
2023-09-04 11:22 dpdklab
2023-09-04 11:24 dpdklab
2023-09-04 11:29 dpdklab
2023-09-04 11:29 dpdklab
2023-09-05 15:01 dpdklab
2023-09-05 15:01 dpdklab
2023-09-06 2:54 dpdklab
2023-09-06 2:59 dpdklab
2023-09-06 3:04 dpdklab
2023-09-06 3:20 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=64f5a652.c80a0220.78ba8.0580SMTPIN_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).