From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu, Jerin Jacob <jerinj@marvell.com>
Subject: |SUCCESS| [GIT MASTER] 52a4028e4c33df32c691aa88751a659534b9ef02
Date: Thu, 19 Sep 2024 11:12:04 -0700 (PDT) [thread overview]
Message-ID: <66ec6974.050a0220.dd3c.4347SMTPIN_ADDED_MISSING@mx.google.com> (raw)
_Functional Testing PASS_
Branch: dpdk-next-eventdev
52a4028e4c33df32c691aa88751a659534b9ef02 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#182422
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 XL710-QDA2 40000 Mbps
Aggregate Results by Test Suite
+-----------------------------+--------+
| Test Suite | Result |
+=============================+========+
| unit_tests_mbuf | PASS |
+-----------------------------+--------+
| vhost_virtio_user_interrupt | PASS |
+-----------------------------+--------+
| virtio_smoke | PASS |
+-----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/tarballs/30670/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-09-19 18:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 18:12 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-20 0:53 dpdklab
2024-09-20 0:45 dpdklab
2024-09-20 0:34 dpdklab
2024-09-19 21:46 dpdklab
2024-09-19 21:45 dpdklab
2024-09-19 20:06 dpdklab
2024-09-19 19:22 dpdklab
2024-09-19 18:21 dpdklab
2024-09-19 18:08 dpdklab
2024-09-19 18:00 dpdklab
2024-09-19 17:50 dpdklab
2024-09-19 17:41 dpdklab
2024-09-19 17:39 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=66ec6974.050a0220.dd3c.4347SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=jerinj@marvell.com \
--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).