From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139210-139214 [PATCH] [v3,5/5] vhost: manage FD with epo
Date: Tue, 09 Apr 2024 05:35:16 -0700 (PDT) [thread overview]
Message-ID: <66153604.050a0220.b3ed.e70eSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240409114845.1336403-6-maxime.coquelin@redhat.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/139214
_Functional Testing PASS_
Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Tuesday, April 09 2024 11:48:45
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:deedfb86a7a6e10064d3cccd593f62072de96e36
139210-139214 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 5.15.0-97-generic
Compiler: gcc 11.4.0
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: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/4
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-83-generic aarch64
Compiler: gcc 11.4.0
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/29747/
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-04-09 12:35 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240409114845.1336403-6-maxime.coquelin@redhat.com>
2024-04-09 11:25 ` |SUCCESS| pw139210-139214 [PATCH v3 5/5] vhost: manage FD with epoll qemudev
2024-04-09 11:30 ` qemudev
2024-04-09 11:49 ` |SUCCESS| pw139214 " checkpatch
2024-04-09 12:31 ` |SUCCESS| pw139210-139214 [PATCH] [v3,5/5] vhost: manage FD with epo dpdklab
2024-04-09 12:31 ` dpdklab
2024-04-09 12:32 ` dpdklab
2024-04-09 12:32 ` dpdklab
2024-04-09 12:32 ` dpdklab
2024-04-09 12:32 ` dpdklab
2024-04-09 12:33 ` dpdklab
2024-04-09 12:33 ` dpdklab
2024-04-09 12:33 ` dpdklab
2024-04-09 12:34 ` dpdklab
2024-04-09 12:34 ` dpdklab
2024-04-09 12:35 ` dpdklab
2024-04-09 12:35 ` dpdklab [this message]
2024-04-09 12:35 ` dpdklab
2024-04-09 12:35 ` dpdklab
2024-04-09 12:36 ` dpdklab
2024-04-09 12:36 ` dpdklab
2024-04-09 12:36 ` dpdklab
2024-04-09 12:37 ` dpdklab
2024-04-09 12:37 ` dpdklab
2024-04-09 12:37 ` dpdklab
2024-04-09 12:37 ` dpdklab
2024-04-09 12:38 ` dpdklab
2024-04-09 12:38 ` dpdklab
2024-04-09 12:38 ` dpdklab
2024-04-09 12:38 ` dpdklab
2024-04-09 12:38 ` dpdklab
2024-04-09 12:38 ` dpdklab
2024-04-09 12:39 ` dpdklab
2024-04-09 12:39 ` dpdklab
2024-04-09 12:39 ` dpdklab
2024-04-09 12:39 ` dpdklab
2024-04-09 12:39 ` dpdklab
2024-04-09 12:40 ` dpdklab
2024-04-09 12:40 ` dpdklab
2024-04-09 12:40 ` dpdklab
2024-04-09 12:41 ` dpdklab
2024-04-09 12:41 ` dpdklab
2024-04-09 12:42 ` dpdklab
2024-04-09 12:43 ` dpdklab
2024-04-09 12:43 ` dpdklab
2024-04-09 12:43 ` dpdklab
2024-04-09 12:43 ` dpdklab
2024-04-09 12:44 ` dpdklab
2024-04-09 12:44 ` dpdklab
2024-04-09 12:44 ` |SUCCESS| pw139214 [PATCH v3 5/5] vhost: manage FD with epoll 0-day Robot
2024-04-09 12:47 ` |SUCCESS| pw139210-139214 [PATCH] [v3,5/5] vhost: manage FD with epo dpdklab
2024-04-09 12:48 ` dpdklab
2024-04-09 12:49 ` dpdklab
2024-04-09 12:51 ` dpdklab
2024-04-09 12:52 ` dpdklab
2024-04-09 12:53 ` dpdklab
2024-04-09 12:53 ` dpdklab
2024-04-09 12:54 ` dpdklab
2024-04-09 12:59 ` dpdklab
2024-04-09 13:00 ` dpdklab
2024-04-09 13:00 ` dpdklab
2024-04-09 13:00 ` dpdklab
2024-04-09 13:00 ` dpdklab
2024-04-09 13:01 ` dpdklab
2024-04-09 13:02 ` dpdklab
2024-04-09 13:03 ` dpdklab
2024-04-09 13:03 ` dpdklab
2024-04-09 13:03 ` dpdklab
2024-04-09 13:04 ` dpdklab
2024-04-09 13:05 ` dpdklab
2024-04-09 13:07 ` dpdklab
2024-04-09 13:07 ` dpdklab
2024-04-09 13:10 ` dpdklab
2024-04-09 13:11 ` dpdklab
2024-04-09 13:11 ` dpdklab
2024-04-09 13:12 ` dpdklab
2024-04-09 13:14 ` dpdklab
2024-04-09 13:16 ` dpdklab
2024-04-09 13:17 ` dpdklab
2024-04-09 13:18 ` dpdklab
2024-04-09 13:19 ` dpdklab
2024-04-09 13:20 ` dpdklab
2024-04-09 13:23 ` dpdklab
2024-04-09 13:26 ` dpdklab
2024-04-09 13:28 ` dpdklab
2024-04-09 13:30 ` dpdklab
2024-04-09 13:32 ` dpdklab
2024-04-09 13:32 ` dpdklab
2024-04-09 13:38 ` dpdklab
2024-04-09 14:00 ` dpdklab
2024-04-09 14:05 ` dpdklab
2024-04-09 14:41 ` dpdklab
2024-04-09 15:18 ` dpdklab
2024-04-09 16:23 ` 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=66153604.050a0220.b3ed.e70eSMTPIN_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).