From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129337 [PATCH] [v2] app/crypto-perf: fix socket ID defau
Date: Wed, 12 Jul 2023 11:49:13 -0700 (PDT) [thread overview]
Message-ID: <64aef5a9.020a0220.d6fcc.69d1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/129337
_Functional Testing PASS_
Submitter: Power, Ciara <ciara.power@intel.com>
Date: Thursday, July 06 2023 10:51:51
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a64a4564705d18d20d20cfa16c79e795b7bf0f1e
129337 --> 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/26997/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-12 18:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 18:49 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-14 13:21 dpdklab
2023-07-14 13:21 dpdklab
2023-07-13 9:53 dpdklab
2023-07-13 9:48 dpdklab
2023-07-13 9:43 dpdklab
2023-07-12 20:07 dpdklab
2023-07-12 20:03 dpdklab
2023-07-12 18:49 dpdklab
2023-07-11 2:33 dpdklab
2023-07-08 17:44 dpdklab
2023-07-08 17:28 dpdklab
2023-07-07 3:26 dpdklab
2023-07-06 19:49 dpdklab
2023-07-06 19:41 dpdklab
2023-07-06 19:26 dpdklab
2023-07-06 11:57 dpdklab
2023-07-06 11:56 dpdklab
2023-07-06 11:51 dpdklab
2023-07-06 11:50 dpdklab
2023-07-06 11:49 dpdklab
2023-07-06 11:45 dpdklab
2023-07-06 11:43 dpdklab
2023-07-06 11:42 dpdklab
2023-07-06 11:34 dpdklab
2023-07-06 11:33 dpdklab
2023-07-06 11:32 dpdklab
2023-07-06 11:32 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=64aef5a9.020a0220.d6fcc.69d1SMTPIN_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).