From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw148312 [PATCH] net/iavf: add segment-length check to Tx
Date: Mon, 11 Nov 2024 19:49:54 -0800 (PST) [thread overview]
Message-ID: <6732d062.050a0220.3256ac.6413SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241111164221.3031276-1-bruce.richardson@intel.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/148312
_Functional Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Monday, November 11 2024 16:42:20
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7b121820e14bbd24197f83c9bbbe43883623b01e
148312 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#195511
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/patchsets/31885/
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-11-12 3:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241111164221.3031276-1-bruce.richardson@intel.com>
2024-11-11 16:11 ` |SUCCESS| pw148312 [PATCH] net/iavf: add segment-length check to Tx prep qemudev
2024-11-11 16:15 ` qemudev
2024-11-11 16:43 ` checkpatch
2024-11-11 18:45 ` 0-day Robot
2024-11-12 3:44 ` |SUCCESS| pw148312 [PATCH] net/iavf: add segment-length check to Tx dpdklab
2024-11-12 3:46 ` dpdklab
2024-11-12 3:47 ` dpdklab
2024-11-12 3:49 ` dpdklab [this message]
2024-11-12 3:56 ` dpdklab
2024-11-12 3:59 ` |PENDING| " dpdklab
2024-11-12 4:02 ` |SUCCESS| " dpdklab
2024-11-12 4:02 ` |PENDING| " dpdklab
2024-11-12 4:12 ` |SUCCESS| " dpdklab
2024-11-12 4:27 ` dpdklab
2024-11-12 4:31 ` dpdklab
2024-11-12 4:35 ` dpdklab
2024-11-12 4:36 ` |WARNING| " dpdklab
2024-11-12 4:39 ` |SUCCESS| " dpdklab
2024-11-12 4:50 ` dpdklab
2024-11-12 5:11 ` dpdklab
2024-11-12 6:46 ` 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=6732d062.050a0220.3256ac.6413SMTPIN_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).