From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137984 [PATCH] vhost: fix vring addr update with vDPA
Date: Tue, 05 Mar 2024 08:16:45 -0800 (PST) [thread overview]
Message-ID: <65e7456d.050a0220.fa2e9.916aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240305091326.2697724-1-david.marchand@redhat.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137984
_Functional Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Tuesday, March 05 2024 09:13:25
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:deedfb86a7a6e10064d3cccd593f62072de96e36
137984 --> 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
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
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/3
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 9.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29412/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-03-05 16:16 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240305091326.2697724-1-david.marchand@redhat.com>
2024-03-05 8:54 ` qemudev
2024-03-05 8:58 ` qemudev
2024-03-05 9:15 ` checkpatch
2024-03-05 10:05 ` 0-day Robot
2024-03-05 10:46 ` |WARNING| " dpdklab
2024-03-05 15:53 ` |SUCCESS| " dpdklab
2024-03-05 16:06 ` dpdklab
2024-03-05 16:06 ` dpdklab
2024-03-05 16:08 ` dpdklab
2024-03-05 16:09 ` dpdklab
2024-03-05 16:10 ` dpdklab
2024-03-05 16:16 ` dpdklab [this message]
2024-03-05 16:18 ` dpdklab
2024-03-05 16:31 ` dpdklab
2024-03-05 16:32 ` dpdklab
2024-03-05 16:32 ` dpdklab
2024-03-05 16:32 ` dpdklab
2024-03-05 16:32 ` dpdklab
2024-03-05 16:35 ` dpdklab
2024-03-05 16:39 ` dpdklab
2024-03-05 16:40 ` dpdklab
2024-03-05 16:41 ` dpdklab
2024-03-05 16:41 ` dpdklab
2024-03-05 16:49 ` dpdklab
2024-03-05 18:01 ` dpdklab
2024-03-05 18:01 ` dpdklab
2024-03-05 18:03 ` dpdklab
2024-03-05 18:03 ` dpdklab
2024-03-05 18:04 ` dpdklab
2024-03-05 18:05 ` dpdklab
2024-03-05 18:06 ` dpdklab
2024-03-05 18:16 ` dpdklab
2024-03-05 18:17 ` dpdklab
2024-03-05 18:17 ` dpdklab
2024-03-05 18:23 ` dpdklab
2024-03-05 18:24 ` dpdklab
2024-03-05 19:03 ` dpdklab
2024-03-05 19:05 ` dpdklab
2024-03-05 19:14 ` dpdklab
2024-03-05 19:14 ` dpdklab
2024-03-05 19:15 ` dpdklab
2024-03-05 19:18 ` dpdklab
2024-03-05 19:19 ` dpdklab
2024-03-05 19:20 ` dpdklab
2024-03-05 19:31 ` dpdklab
2024-03-05 19:53 ` dpdklab
2024-03-05 20:21 ` dpdklab
2024-03-09 17:32 ` dpdklab
2024-03-09 18:05 ` 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=65e7456d.050a0220.fa2e9.916aSMTPIN_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).