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| pw121092 [PATCH] [v2] net/iavf: add lock for vf commands
Date: Tue, 20 Dec 2022 11:21:56 -0500 (EST) [thread overview]
Message-ID: <20221220162156.49D3E19DB7@noxus.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 781 bytes --]
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/121092
_Functional Testing PASS_
Submitter: Mike Pattrick <mkp@redhat.com>
Date: Tuesday, December 20 2022 15:54:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:c581c49cd3fcaff596fbe566e270b442e6326c79
121092 --> functional testing pass
Test environment and result as below:
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/2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/24784/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2022-12-20 16:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 16:21 dpdklab [this message]
2022-12-20 16:23 dpdklab
2022-12-20 16:26 dpdklab
2022-12-20 16:27 dpdklab
2022-12-20 16:31 dpdklab
2022-12-20 16:37 dpdklab
[not found] <20221220155414.266309-1-mkp@redhat.com>
2022-12-20 15:47 ` |SUCCESS| pw121092 [PATCH v2] " qemudev
2022-12-20 15:51 ` qemudev
2022-12-20 15:55 ` checkpatch
2022-12-20 16:39 ` 0-day Robot
2022-12-20 16:42 |SUCCESS| pw121092 [PATCH] [v2] " dpdklab
2022-12-20 17:19 dpdklab
2022-12-20 17:23 dpdklab
2022-12-20 17:28 dpdklab
2022-12-20 17:35 dpdklab
2022-12-20 17:47 dpdklab
2022-12-20 18:00 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=20221220162156.49D3E19DB7@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).