From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143679-143681 [PATCH] [RFC,3/3] vduse: use import VDUSE
Date: Thu, 05 Sep 2024 17:21:23 -0700 (PDT) [thread overview]
Message-ID: <66da4b03.170a0220.cb6e.10a4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240905221528.1861323-4-maxime.coquelin@redhat.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143681
_Functional Testing PASS_
Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Thursday, September 05 2024 22:15:28
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
143679-143681 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#178739
Test environment and result as below:
Ubuntu 20.04
Kernel: 5.4.0-122-generic
Compiler: gcc 9.4.0
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| scatter | PASS |
+-----------------------------+--------+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30930/
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-09-06 0:21 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240905221528.1861323-4-maxime.coquelin@redhat.com>
2024-09-05 23:04 ` |FAILURE| pw143681 [RFC 3/3] vduse: use import VDUSE uAPI header 0-day Robot
2024-09-06 0:07 ` |SUCCESS| pw143679-143681 [PATCH] [RFC,3/3] vduse: use import VDUSE dpdklab
2024-09-06 0:21 ` dpdklab [this message]
2024-09-06 1:11 ` |PENDING| " dpdklab
2024-09-06 1:27 ` |FAILURE| " dpdklab
2024-09-06 1:59 ` |SUCCESS| " dpdklab
2024-09-06 3:05 ` dpdklab
2024-09-06 3:12 ` dpdklab
2024-09-06 5:44 ` dpdklab
2024-09-06 6:21 ` |PENDING| " dpdklab
2024-09-06 6:36 ` |SUCCESS| " dpdklab
2024-09-06 6:38 ` |FAILURE| " dpdklab
2024-09-06 6:49 ` dpdklab
2024-09-06 6:50 ` dpdklab
2024-09-06 6:50 ` dpdklab
2024-09-06 6:51 ` dpdklab
2024-09-06 6:52 ` dpdklab
2024-09-06 6:52 ` |SUCCESS| " dpdklab
2024-09-06 6:53 ` |FAILURE| " dpdklab
2024-09-06 6:55 ` dpdklab
2024-09-06 6:56 ` dpdklab
2024-09-06 6:58 ` dpdklab
2024-09-06 6:59 ` dpdklab
2024-09-06 7:00 ` dpdklab
2024-09-06 7:10 ` dpdklab
2024-09-06 7:10 ` |SUCCESS| " dpdklab
2024-09-06 7:11 ` dpdklab
2024-09-06 7:12 ` dpdklab
2024-09-06 7:13 ` dpdklab
2024-09-06 7:14 ` dpdklab
2024-09-06 7:15 ` dpdklab
2024-09-06 7:59 ` dpdklab
2024-09-06 10:16 ` dpdklab
2024-09-06 10:18 ` dpdklab
2024-09-06 10:19 ` dpdklab
2024-09-06 10:20 ` dpdklab
2024-09-06 10:33 ` dpdklab
2024-09-06 10:37 ` dpdklab
2024-09-06 10:39 ` dpdklab
2024-09-06 10:41 ` dpdklab
2024-09-06 10:57 ` dpdklab
2024-09-06 10:58 ` dpdklab
2024-09-06 11:20 ` dpdklab
2024-09-06 11:26 ` dpdklab
2024-09-06 13:35 ` dpdklab
2024-09-06 13:36 ` dpdklab
2024-09-06 13:39 ` dpdklab
2024-09-06 13:40 ` dpdklab
2024-09-06 13:41 ` dpdklab
2024-09-06 13:42 ` dpdklab
2024-09-06 13:42 ` dpdklab
2024-09-06 13:43 ` dpdklab
2024-09-06 14:38 ` dpdklab
2024-09-06 14:41 ` dpdklab
2024-09-06 15:02 ` dpdklab
2024-09-06 15:03 ` dpdklab
2024-09-06 15:04 ` dpdklab
2024-09-06 15:06 ` dpdklab
2024-09-06 15:17 ` dpdklab
2024-09-06 15:24 ` dpdklab
2024-09-06 15:25 ` dpdklab
2024-09-06 15:27 ` dpdklab
2024-09-07 18:26 ` dpdklab
2024-09-07 18:55 ` dpdklab
2024-09-17 16:56 ` dpdklab
2024-09-17 17:15 ` dpdklab
2024-09-17 17:27 ` dpdklab
2024-09-17 17:48 ` 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=66da4b03.170a0220.cb6e.10a4SMTPIN_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).