From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw129329-129328 [PATCH] [v2,2/2] vhost: fix vduse features
Date: Wed, 12 Jul 2023 11:50:57 -0700 (PDT) [thread overview]
Message-ID: <64aef611.0d0a0220.4b342.4b03SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/129328
_Functional Testing PASS_
Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Thursday, July 06 2023 08:12:23
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a64a4564705d18d20d20cfa16c79e795b7bf0f1e
129329-129328 --> functional testing pass
Test environment and result as below:
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
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26994/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-07-12 18:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 18:50 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-07-14 15:06 dpdklab
2023-07-14 15:05 dpdklab
2023-07-13 9:09 dpdklab
2023-07-13 9:04 dpdklab
2023-07-13 8:59 dpdklab
2023-07-12 19:31 dpdklab
2023-07-12 19:28 dpdklab
2023-07-12 18:11 dpdklab
2023-07-11 1:56 dpdklab
2023-07-08 15:19 dpdklab
2023-07-08 14:59 dpdklab
2023-07-07 2:23 dpdklab
2023-07-06 18:25 dpdklab
2023-07-06 17:06 dpdklab
2023-07-06 15:08 dpdklab
2023-07-06 9:28 dpdklab
2023-07-06 9:23 dpdklab
2023-07-06 9:19 dpdklab
2023-07-06 9:19 dpdklab
2023-07-06 9:15 dpdklab
2023-07-06 9:10 dpdklab
2023-07-06 9:08 dpdklab
2023-07-06 9:04 dpdklab
2023-07-06 9:00 dpdklab
2023-07-06 8:57 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=64aef611.0d0a0220.4b342.4b03SMTPIN_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).