From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137339 [PATCH] [v4] vhost: enhance virtqueue access lock
Date: Thu, 29 Feb 2024 02:59:29 -0800 (PST) [thread overview]
Message-ID: <65e06391.050a0220.a42a2.33a0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227103903.1338151-1-david.marchand@redhat.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137339
_Functional Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Tuesday, February 27 2024 10:39:03
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137339 --> functional testing pass
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.82
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
Arm Ampere Altra - Ubuntu 22.04.3
Kernel: 5.15.0-82
Compiler: gcc 11.4.0
NIC: Broadcom Inc. and subsidiaries BCM957508-P2100G Dual-Port 100 Gb/s QSFP56 100 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29283/
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-02-29 10:59 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240227103903.1338151-1-david.marchand@redhat.com>
2024-02-27 10:20 ` |SUCCESS| pw137339 [PATCH v4] vhost: enhance virtqueue access lock asserts qemudev
2024-02-27 10:25 ` qemudev
2024-02-27 10:39 ` |WARNING| " checkpatch
2024-02-27 11:45 ` |SUCCESS| " 0-day Robot
2024-02-27 19:45 ` |SUCCESS| pw137339 [PATCH] [v4] vhost: enhance virtqueue access lock dpdklab
2024-02-27 19:46 ` dpdklab
2024-02-27 19:46 ` dpdklab
2024-02-27 19:46 ` dpdklab
2024-02-27 19:47 ` dpdklab
2024-02-27 19:55 ` dpdklab
2024-02-27 19:55 ` dpdklab
2024-02-27 19:55 ` dpdklab
2024-02-27 19:56 ` dpdklab
2024-02-27 19:56 ` dpdklab
2024-02-27 19:57 ` dpdklab
2024-02-27 19:58 ` dpdklab
2024-02-27 19:58 ` dpdklab
2024-02-27 19:59 ` dpdklab
2024-02-27 19:59 ` dpdklab
2024-02-27 19:59 ` dpdklab
2024-02-27 19:59 ` dpdklab
2024-02-27 20:00 ` dpdklab
2024-02-27 20:00 ` dpdklab
2024-02-27 20:02 ` dpdklab
2024-02-27 20:02 ` dpdklab
2024-02-27 20:03 ` dpdklab
2024-02-27 20:03 ` dpdklab
2024-02-27 20:04 ` dpdklab
2024-02-27 20:04 ` dpdklab
2024-02-27 20:04 ` dpdklab
2024-02-27 20:04 ` dpdklab
2024-02-27 20:05 ` dpdklab
2024-02-27 20:05 ` dpdklab
2024-02-27 20:05 ` dpdklab
2024-02-27 20:05 ` dpdklab
2024-02-27 20:06 ` dpdklab
2024-02-27 20:06 ` dpdklab
2024-02-27 20:06 ` dpdklab
2024-02-27 20:06 ` dpdklab
2024-02-27 20:13 ` dpdklab
2024-02-27 20:23 ` dpdklab
2024-02-27 20:42 ` dpdklab
2024-02-27 20:45 ` dpdklab
2024-02-27 20:46 ` dpdklab
2024-02-27 20:57 ` dpdklab
2024-02-27 20:58 ` dpdklab
2024-02-27 21:00 ` dpdklab
2024-02-27 21:01 ` dpdklab
2024-02-27 21:03 ` dpdklab
2024-02-27 23:30 ` dpdklab
2024-02-28 1:09 ` dpdklab
2024-02-28 7:04 ` dpdklab
2024-02-28 7:08 ` dpdklab
2024-02-28 8:56 ` dpdklab
2024-02-28 17:30 ` dpdklab
2024-02-29 10:44 ` dpdklab
2024-02-29 10:49 ` dpdklab
2024-02-29 10:54 ` dpdklab
2024-02-29 10:59 ` dpdklab [this message]
2024-02-27 16:03 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-02-27 15:44 dpdklab
2024-02-27 15:41 dpdklab
2024-02-27 15:31 dpdklab
2024-02-27 15:22 dpdklab
2024-02-27 15:22 dpdklab
2024-02-27 15:22 dpdklab
2024-02-27 14:58 dpdklab
2024-02-27 14:52 dpdklab
2024-02-27 14:52 dpdklab
2024-02-27 14:50 dpdklab
2024-02-27 14:47 dpdklab
2024-02-27 14:27 dpdklab
2024-02-27 14:23 dpdklab
2024-02-27 14:19 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=65e06391.050a0220.a42a2.33a0SMTPIN_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).