From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143377 [PATCH] [v3] net/cpfl: fix cpfl parser issue
Date: Fri, 23 Aug 2024 08:57:03 -0700 (PDT) [thread overview]
Message-ID: <66c8b14f.020a0220.35a89f.7f7cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240823111450.1738434-1-praveen.shetty@intel.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143377
_Functional Testing PASS_
Submitter: Praveen Shetty <praveen.shetty@intel.com>
Date: Friday, August 23 2024 11:14:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:22637bd9a8c26f20bf12b69f90f085d50eda9d66
143377 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#176726
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 |
+=============================+========+
| 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/30845/
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-08-23 15:57 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240823111450.1738434-1-praveen.shetty@intel.com>
2024-08-23 10:51 ` |SUCCESS| pw143377 [PATCH v3] " qemudev
2024-08-23 10:56 ` qemudev
2024-08-23 11:16 ` checkpatch
2024-08-23 12:04 ` 0-day Robot
2024-08-23 15:25 ` |SUCCESS| pw143377 [PATCH] [v3] " dpdklab
2024-08-23 15:31 ` dpdklab
2024-08-23 15:44 ` dpdklab
2024-08-23 15:57 ` dpdklab [this message]
2024-08-23 16:05 ` dpdklab
2024-08-23 16:30 ` dpdklab
2024-08-23 16:44 ` dpdklab
2024-08-23 16:50 ` dpdklab
2024-08-23 16:55 ` dpdklab
2024-08-23 17:40 ` dpdklab
2024-08-23 17:45 ` dpdklab
2024-08-23 17:54 ` dpdklab
2024-08-23 17:54 ` dpdklab
2024-08-23 18:00 ` dpdklab
2024-08-23 18:05 ` dpdklab
2024-08-23 18:27 ` dpdklab
2024-08-23 19:09 ` dpdklab
2024-08-23 19:16 ` dpdklab
2024-08-23 19:23 ` dpdklab
2024-08-23 19:33 ` dpdklab
2024-08-23 21:56 ` dpdklab
2024-08-23 22:01 ` dpdklab
2024-08-23 22:25 ` dpdklab
2024-08-23 22:36 ` dpdklab
2024-08-23 22:40 ` dpdklab
2024-08-23 22:43 ` dpdklab
2024-08-24 1:40 ` |PENDING| " dpdklab
2024-08-24 1:47 ` |SUCCESS| " dpdklab
2024-08-24 1:53 ` |FAILURE| " dpdklab
2024-08-24 2:20 ` |WARNING| " dpdklab
2024-08-24 3:11 ` |SUCCESS| " dpdklab
2024-08-24 3:46 ` dpdklab
2024-08-24 3:55 ` |PENDING| " dpdklab
2024-08-24 4:07 ` |SUCCESS| " dpdklab
2024-08-24 4:09 ` dpdklab
2024-08-24 4:16 ` dpdklab
2024-08-24 4:16 ` dpdklab
2024-08-24 4:23 ` dpdklab
2024-08-24 4:24 ` dpdklab
2024-08-24 4:25 ` dpdklab
2024-08-24 4:26 ` dpdklab
2024-08-24 4:53 ` dpdklab
2024-08-24 8:29 ` dpdklab
2024-08-24 11:16 ` dpdklab
2024-08-24 11:46 ` dpdklab
2024-09-20 17:54 ` dpdklab
2024-09-20 18:06 ` dpdklab
2024-09-20 18:26 ` 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=66c8b14f.020a0220.35a89f.7f7cSMTPIN_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).