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| pw124617 [PATCH] [v3] vhost: fix madvise arguments alignment
Date: Thu, 2 Mar 2023 01:12:37 +0000 (UTC) [thread overview]
Message-ID: <20230302011237.E1904601F7@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/124617
_Functional Testing PASS_
Submitter: Mike Pattrick <mkp@redhat.com>
Date: Wednesday, March 01 2023 20:02:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4ef69b2877a24ddb89afaf4bb6f4e73bb52a605b
124617 --> functional testing pass
Test environment and result as below:
Arm Ampere Altra - Ubuntu 20.04.4
Kernel: 5.4.0-137-generic aarch64
Compiler: gcc 9.4
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
Ubuntu 22.04
Kernel: 5.15.0-58-generic x86_64
Compiler: gcc gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.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/2
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25579/
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-02 1:12 UTC|newest]
Thread overview: 223+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 1:12 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-03 11:48 dpdklab
2023-03-03 11:48 dpdklab
2023-03-03 11:10 dpdklab
2023-03-03 11:08 dpdklab
2023-03-03 11:06 dpdklab
2023-03-03 10:59 dpdklab
2023-03-03 10:57 dpdklab
2023-03-03 10:53 dpdklab
2023-03-03 10:52 dpdklab
2023-03-03 10:48 dpdklab
2023-03-03 10:48 dpdklab
2023-03-03 10:44 dpdklab
2023-03-03 10:41 dpdklab
2023-03-03 10:39 dpdklab
2023-03-03 9:18 dpdklab
2023-03-03 9:18 dpdklab
2023-03-03 9:14 dpdklab
2023-03-03 9:08 dpdklab
2023-03-03 9:06 dpdklab
2023-03-03 9:04 dpdklab
2023-03-03 8:56 dpdklab
2023-03-03 8:53 dpdklab
2023-03-03 8:48 dpdklab
2023-03-03 8:47 dpdklab
2023-03-03 8:40 dpdklab
2023-03-03 8:29 dpdklab
2023-03-03 8:29 dpdklab
2023-03-03 8:26 dpdklab
2023-03-03 8:15 dpdklab
2023-03-03 8:09 dpdklab
2023-03-03 7:53 dpdklab
2023-03-03 7:51 dpdklab
2023-03-03 7:49 dpdklab
2023-03-03 7:48 dpdklab
2023-03-03 7:46 dpdklab
2023-03-03 7:44 dpdklab
2023-03-03 7:39 dpdklab
2023-03-03 7:37 dpdklab
2023-03-03 7:35 dpdklab
2023-03-03 7:26 dpdklab
2023-03-03 7:25 dpdklab
2023-03-03 7:25 dpdklab
2023-03-03 7:24 dpdklab
2023-03-03 7:12 dpdklab
2023-03-03 6:49 dpdklab
2023-03-03 6:47 dpdklab
2023-03-03 6:45 dpdklab
2023-03-03 6:33 dpdklab
2023-03-03 6:30 dpdklab
2023-03-03 6:25 dpdklab
2023-03-03 6:22 dpdklab
2023-03-03 6:19 dpdklab
2023-03-03 6:15 dpdklab
2023-03-03 6:05 dpdklab
2023-03-03 6:00 dpdklab
2023-03-03 5:00 dpdklab
2023-03-03 5:00 dpdklab
2023-03-03 4:55 dpdklab
2023-03-03 4:48 dpdklab
2023-03-03 4:16 dpdklab
2023-03-03 4:13 dpdklab
2023-03-03 4:11 dpdklab
2023-03-03 4:11 dpdklab
2023-03-03 4:09 dpdklab
2023-03-03 4:07 dpdklab
2023-03-03 4:07 dpdklab
2023-03-03 4:04 dpdklab
2023-03-03 4:02 dpdklab
2023-03-03 4:00 dpdklab
2023-03-03 3:56 dpdklab
2023-03-03 3:54 dpdklab
2023-03-03 3:46 dpdklab
2023-03-03 3:46 dpdklab
2023-03-03 3:45 dpdklab
2023-03-03 3:39 dpdklab
2023-03-03 3:34 dpdklab
2023-03-03 3:34 dpdklab
2023-03-03 3:28 dpdklab
2023-03-03 3:22 dpdklab
2023-03-03 3:16 dpdklab
2023-03-03 3:10 dpdklab
2023-03-03 3:08 dpdklab
2023-03-03 3:08 dpdklab
2023-03-03 3:07 dpdklab
2023-03-03 3:05 dpdklab
2023-03-03 2:11 dpdklab
2023-03-03 2:10 dpdklab
2023-03-03 1:48 dpdklab
2023-03-03 1:48 dpdklab
2023-03-03 1:46 dpdklab
2023-03-03 1:44 dpdklab
2023-03-03 1:39 dpdklab
2023-03-03 1:38 dpdklab
2023-03-03 1:35 dpdklab
2023-03-03 1:32 dpdklab
2023-03-03 1:31 dpdklab
2023-03-03 1:30 dpdklab
2023-03-03 1:20 dpdklab
2023-03-03 1:18 dpdklab
2023-03-02 14:08 dpdklab
2023-03-02 12:35 dpdklab
2023-03-02 12:24 dpdklab
2023-03-02 11:38 dpdklab
2023-03-02 10:54 dpdklab
2023-03-02 10:45 dpdklab
2023-03-02 10:18 dpdklab
2023-03-02 9:52 dpdklab
2023-03-02 9:50 dpdklab
2023-03-02 9:41 dpdklab
2023-03-02 8:58 dpdklab
2023-03-02 8:51 dpdklab
2023-03-02 8:42 dpdklab
2023-03-02 7:50 dpdklab
2023-03-02 7:45 dpdklab
2023-03-02 6:44 dpdklab
2023-03-02 5:06 dpdklab
2023-03-02 4:54 dpdklab
2023-03-02 4:31 dpdklab
2023-03-02 4:19 dpdklab
2023-03-02 4:02 dpdklab
2023-03-02 3:41 dpdklab
2023-03-02 3:34 dpdklab
2023-03-02 3:29 dpdklab
2023-03-02 3:21 dpdklab
2023-03-02 3:16 dpdklab
2023-03-02 3:14 dpdklab
2023-03-02 3:14 dpdklab
2023-03-02 3:14 dpdklab
2023-03-02 3:13 dpdklab
2023-03-02 3:05 dpdklab
2023-03-02 2:56 dpdklab
2023-03-02 2:48 dpdklab
2023-03-02 2:44 dpdklab
2023-03-02 2:37 dpdklab
2023-03-02 2:24 dpdklab
2023-03-02 2:19 dpdklab
2023-03-02 2:07 dpdklab
2023-03-02 2:04 dpdklab
2023-03-02 1:54 dpdklab
2023-03-02 1:52 dpdklab
2023-03-02 1:43 dpdklab
2023-03-02 1:39 dpdklab
2023-03-02 1:38 dpdklab
2023-03-02 1:32 dpdklab
2023-03-02 1:26 dpdklab
2023-03-02 1:18 dpdklab
2023-03-02 1:09 dpdklab
2023-03-02 1:09 dpdklab
2023-03-02 1:07 dpdklab
2023-03-02 1:00 dpdklab
2023-03-02 0:56 dpdklab
2023-03-02 0:53 dpdklab
2023-03-02 0:52 dpdklab
2023-03-02 0:49 dpdklab
2023-03-02 0:45 dpdklab
2023-03-02 0:39 dpdklab
2023-03-02 0:31 dpdklab
2023-03-02 0:19 dpdklab
2023-03-02 0:18 dpdklab
2023-03-02 0:13 dpdklab
2023-03-02 0:13 dpdklab
2023-03-02 0:11 dpdklab
2023-03-02 0:09 dpdklab
2023-03-02 0:07 dpdklab
2023-03-02 0:06 dpdklab
2023-03-02 0:02 dpdklab
2023-03-01 23:59 dpdklab
2023-03-01 23:58 dpdklab
2023-03-01 23:56 dpdklab
2023-03-01 23:53 dpdklab
2023-03-01 23:51 dpdklab
2023-03-01 23:49 dpdklab
2023-03-01 23:47 dpdklab
2023-03-01 23:39 dpdklab
2023-03-01 23:39 dpdklab
2023-03-01 23:39 dpdklab
2023-03-01 23:38 dpdklab
2023-03-01 23:38 dpdklab
2023-03-01 23:35 dpdklab
2023-03-01 23:35 dpdklab
2023-03-01 23:35 dpdklab
2023-03-01 23:29 dpdklab
2023-03-01 23:26 dpdklab
2023-03-01 23:23 dpdklab
2023-03-01 23:23 dpdklab
2023-03-01 23:19 dpdklab
2023-03-01 23:15 dpdklab
2023-03-01 23:14 dpdklab
2023-03-01 23:11 dpdklab
2023-03-01 23:09 dpdklab
2023-03-01 23:09 dpdklab
2023-03-01 23:07 dpdklab
2023-03-01 23:06 dpdklab
2023-03-01 23:02 dpdklab
2023-03-01 22:58 dpdklab
2023-03-01 22:55 dpdklab
2023-03-01 22:55 dpdklab
2023-03-01 22:51 dpdklab
2023-03-01 22:48 dpdklab
2023-03-01 22:45 dpdklab
2023-03-01 22:42 dpdklab
2023-03-01 22:41 dpdklab
2023-03-01 22:35 dpdklab
2023-03-01 22:33 dpdklab
2023-03-01 22:31 dpdklab
2023-03-01 22:28 dpdklab
2023-03-01 22:28 dpdklab
2023-03-01 22:17 dpdklab
2023-03-01 22:16 dpdklab
2023-03-01 22:13 dpdklab
2023-03-01 22:03 dpdklab
2023-03-01 21:56 dpdklab
2023-03-01 21:53 dpdklab
2023-03-01 21:51 dpdklab
2023-03-01 21:45 dpdklab
2023-03-01 21:45 dpdklab
2023-03-01 21:40 dpdklab
2023-03-01 21:38 dpdklab
[not found] <20230301200228.1477189-1-mkp@redhat.com>
2023-03-01 19:52 ` |SUCCESS| pw124617 [PATCH v3] " qemudev
2023-03-01 19:56 ` qemudev
2023-03-01 20:03 ` checkpatch
2023-03-01 21:59 ` 0-day Robot
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=20230302011237.E1904601F7@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).