From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138099 [PATCH] vhost: fix virtqueue access lock check fo
Date: Thu, 07 Mar 2024 05:42:39 -0800 (PST) [thread overview]
Message-ID: <65e9c44f.170a0220.190f3.723fSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240307103624.610080-1-david.marchand@redhat.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/138099
_Functional Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Thursday, March 07 2024 10:36:24
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:deedfb86a7a6e10064d3cccd593f62072de96e36
138099 --> 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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29461/
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-07 13:42 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240307103624.610080-1-david.marchand@redhat.com>
2024-03-07 10:26 ` |SUCCESS| pw138099 [PATCH] vhost: fix virtqueue access lock check for handlers qemudev
2024-03-07 10:31 ` qemudev
2024-03-07 10:37 ` checkpatch
2024-03-07 11:44 ` 0-day Robot
2024-03-07 13:14 ` |SUCCESS| pw138099 [PATCH] vhost: fix virtqueue access lock check fo dpdklab
2024-03-07 13:42 ` dpdklab [this message]
2024-03-07 13:45 ` dpdklab
2024-03-07 13:51 ` dpdklab
2024-03-07 13:52 ` dpdklab
2024-03-07 13:52 ` dpdklab
2024-03-07 13:58 ` dpdklab
2024-03-07 13:58 ` dpdklab
2024-03-07 13:59 ` dpdklab
2024-03-07 13:59 ` dpdklab
2024-03-07 14:09 ` dpdklab
2024-03-07 14:09 ` dpdklab
2024-03-07 14:10 ` dpdklab
2024-03-07 14:10 ` dpdklab
2024-03-07 14:11 ` dpdklab
2024-03-07 14:11 ` dpdklab
2024-03-07 14:12 ` dpdklab
2024-03-07 14:15 ` dpdklab
2024-03-07 14:38 ` dpdklab
2024-03-07 14:40 ` dpdklab
2024-03-07 14:49 ` dpdklab
2024-03-07 14:49 ` dpdklab
2024-03-07 14:50 ` dpdklab
2024-03-07 14:50 ` dpdklab
2024-03-07 14:52 ` dpdklab
2024-03-07 14:52 ` dpdklab
2024-03-07 14:52 ` dpdklab
2024-03-07 14:52 ` dpdklab
2024-03-07 14:53 ` dpdklab
2024-03-07 14:53 ` dpdklab
2024-03-07 14:53 ` dpdklab
2024-03-07 14:54 ` dpdklab
2024-03-07 14:55 ` dpdklab
2024-03-07 14:56 ` dpdklab
2024-03-07 14:56 ` dpdklab
2024-03-07 14:58 ` dpdklab
2024-03-07 15:00 ` dpdklab
2024-03-07 15:01 ` dpdklab
2024-03-07 15:01 ` dpdklab
2024-03-07 15:02 ` dpdklab
2024-03-07 15:04 ` dpdklab
2024-03-07 15:04 ` dpdklab
2024-03-07 15:08 ` dpdklab
2024-03-07 15:21 ` dpdklab
2024-03-07 15:22 ` dpdklab
2024-03-07 15:22 ` dpdklab
2024-03-07 15:22 ` dpdklab
2024-03-07 15:23 ` dpdklab
2024-03-07 15:23 ` dpdklab
2024-03-07 15:24 ` dpdklab
2024-03-07 15:25 ` dpdklab
2024-03-07 15:25 ` dpdklab
2024-03-07 15:26 ` dpdklab
2024-03-07 15:26 ` dpdklab
2024-03-07 15:27 ` dpdklab
2024-03-07 15:29 ` dpdklab
2024-03-07 15:29 ` dpdklab
2024-03-07 15:37 ` dpdklab
2024-03-07 15:37 ` dpdklab
2024-03-07 15:37 ` dpdklab
2024-03-07 15:45 ` dpdklab
2024-03-07 15:54 ` dpdklab
2024-03-07 15:59 ` dpdklab
2024-03-07 16:18 ` dpdklab
2024-03-07 17:39 ` dpdklab
2024-03-07 17:48 ` dpdklab
2024-03-07 21:36 ` dpdklab
2024-03-08 5:35 ` dpdklab
2024-03-08 5:50 ` dpdklab
2024-03-08 5:54 ` dpdklab
2024-03-08 5:56 ` dpdklab
2024-03-11 21:16 ` dpdklab
2024-03-11 21:51 ` 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=65e9c44f.170a0220.190f3.723fSMTPIN_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).