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| pw124870-124868 [PATCH] [2/2] vhost: refactor to follow new naming convention
Date: Thu, 9 Mar 2023 03:17:08 +0000 (UTC) [thread overview]
Message-ID: <20230309031708.D0B026011F@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/124868
_Functional Testing PASS_
Submitter: Nobuhiro MIKI <nmiki@yahoo-corp.jp>
Date: Thursday, March 09 2023 02:07:21
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8a44b2a511114d9bc658d934d6cf16a3d8150d6d
124870-124868 --> 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/25646/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-03-09 3:17 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-09 3:17 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-09 7:54 dpdklab
2023-03-09 6:12 dpdklab
2023-03-09 5:46 dpdklab
2023-03-09 5:45 dpdklab
2023-03-09 5:37 dpdklab
2023-03-09 5:31 dpdklab
2023-03-09 5:21 dpdklab
2023-03-09 5:20 dpdklab
2023-03-09 5:15 dpdklab
2023-03-09 5:06 dpdklab
2023-03-09 5:03 dpdklab
2023-03-09 5:01 dpdklab
2023-03-09 5:00 dpdklab
2023-03-09 4:55 dpdklab
2023-03-09 4:50 dpdklab
2023-03-09 4:49 dpdklab
2023-03-09 4:48 dpdklab
2023-03-09 4:47 dpdklab
2023-03-09 4:46 dpdklab
2023-03-09 4:45 dpdklab
2023-03-09 4:42 dpdklab
2023-03-09 4:34 dpdklab
2023-03-09 4:30 dpdklab
2023-03-09 4:29 dpdklab
2023-03-09 4:26 dpdklab
2023-03-09 4:22 dpdklab
2023-03-09 4:22 dpdklab
2023-03-09 4:13 dpdklab
2023-03-09 4:10 dpdklab
2023-03-09 4:08 dpdklab
2023-03-09 4:06 dpdklab
2023-03-09 4:06 dpdklab
2023-03-09 4:04 dpdklab
2023-03-09 4:01 dpdklab
2023-03-09 3:55 dpdklab
2023-03-09 3:53 dpdklab
2023-03-09 3:53 dpdklab
2023-03-09 3:51 dpdklab
2023-03-09 3:50 dpdklab
2023-03-09 3:49 dpdklab
2023-03-09 3:48 dpdklab
2023-03-09 3:48 dpdklab
2023-03-09 3:45 dpdklab
2023-03-09 3:44 dpdklab
2023-03-09 3:41 dpdklab
2023-03-09 3:37 dpdklab
2023-03-09 3:37 dpdklab
2023-03-09 3:36 dpdklab
2023-03-09 3:36 dpdklab
2023-03-09 3:33 dpdklab
2023-03-09 3:31 dpdklab
2023-03-09 3:28 dpdklab
2023-03-09 3:28 dpdklab
2023-03-09 3:26 dpdklab
2023-03-09 3:26 dpdklab
2023-03-09 3:22 dpdklab
2023-03-09 3:22 dpdklab
2023-03-09 3:20 dpdklab
2023-03-09 3:20 dpdklab
2023-03-09 3:10 dpdklab
[not found] <20230309020721.22164-3-nmiki@yahoo-corp.jp>
2023-03-09 1:56 ` |SUCCESS| pw124870-124868 [PATCH 2/2] " qemudev
2023-03-09 2:00 ` qemudev
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=20230309031708.D0B026011F@dpdk-ubuntu.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).