From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143536-143565 [PATCH] [v1,30/30] net/i40e: update base d
Date: Mon, 02 Sep 2024 08:33:32 -0700 (PDT) [thread overview]
Message-ID: <66d5dacc.170a0220.3b4e91.1a06SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <27a5279ed4fe3c63c13f8d8f42a5b6be88e5ed53.1725270827.git.anatoly.burakov@intel.com>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143565
_Functional Testing PASS_
Submitter: Burakov, Anatoly <anatoly.burakov@intel.com>
Date: Monday, September 02 2024 09:54:42
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:dfd68009230882b05be48d43a3b14df7875108b8
143536-143565 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#177988
Test environment and result as below:
Ubuntu 20.04.6
Kernel: 5.4.105
Compiler: gcc 9.4
NIC: Marvell CN106XX 50000 Mbps
Target: arm64-native-linuxapp-gcc
Aggregate Results by Test Suite
+-----------------+--------+
| Test Suite | Result |
+=================+========+
| cmdline | PASS |
+-----------------+--------+
| ipv4_reassembly | PASS |
+-----------------+--------+
| l2fwd | PASS |
+-----------------+--------+
| rxtx_callbacks | PASS |
+-----------------+--------+
| tso | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30891/
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-02 15:33 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <27a5279ed4fe3c63c13f8d8f42a5b6be88e5ed53.1725270827.git.anatoly.burakov@intel.com>
2024-09-02 9:38 ` |SUCCESS| pw143536-143565 [PATCH v1 30/30] net/i40e: update base driver README qemudev
2024-09-02 9:42 ` qemudev
2024-09-02 9:59 ` |SUCCESS| pw143565 " checkpatch
2024-09-02 11:04 ` 0-day Robot
2024-09-02 12:51 ` |PENDING| pw143536-143565 [PATCH] [v1,30/30] net/i40e: update base d dpdklab
2024-09-02 12:52 ` |SUCCESS| " dpdklab
2024-09-02 12:53 ` dpdklab
2024-09-02 12:53 ` dpdklab
2024-09-02 12:54 ` dpdklab
2024-09-02 12:55 ` dpdklab
2024-09-02 13:02 ` dpdklab
2024-09-02 13:53 ` |PENDING| " dpdklab
2024-09-02 14:01 ` |SUCCESS| " dpdklab
2024-09-02 14:57 ` dpdklab
2024-09-02 15:24 ` dpdklab
2024-09-02 15:25 ` dpdklab
2024-09-02 15:26 ` dpdklab
2024-09-02 15:27 ` dpdklab
2024-09-02 15:31 ` dpdklab
2024-09-02 15:33 ` dpdklab [this message]
2024-09-02 15:35 ` dpdklab
2024-09-02 15:35 ` dpdklab
2024-09-02 15:37 ` dpdklab
2024-09-02 15:38 ` dpdklab
2024-09-02 15:40 ` dpdklab
2024-09-02 15:40 ` dpdklab
2024-09-02 15:40 ` dpdklab
2024-09-02 15:41 ` dpdklab
2024-09-02 15:41 ` dpdklab
2024-09-02 15:41 ` dpdklab
2024-09-02 15:41 ` dpdklab
2024-09-02 15:42 ` dpdklab
2024-09-02 15:42 ` dpdklab
2024-09-02 15:42 ` dpdklab
2024-09-02 15:43 ` dpdklab
2024-09-02 15:43 ` dpdklab
2024-09-02 15:43 ` dpdklab
2024-09-02 15:43 ` dpdklab
2024-09-02 15:44 ` dpdklab
2024-09-02 15:44 ` dpdklab
2024-09-02 15:44 ` dpdklab
2024-09-02 15:45 ` dpdklab
2024-09-02 15:45 ` dpdklab
2024-09-02 15:45 ` dpdklab
2024-09-02 15:46 ` dpdklab
2024-09-02 15:47 ` dpdklab
2024-09-02 15:47 ` dpdklab
2024-09-02 15:48 ` dpdklab
2024-09-02 15:48 ` dpdklab
2024-09-02 15:48 ` dpdklab
2024-09-02 15:50 ` dpdklab
2024-09-02 15:50 ` dpdklab
2024-09-02 15:53 ` dpdklab
2024-09-02 15:54 ` dpdklab
2024-09-02 15:55 ` dpdklab
2024-09-02 15:55 ` dpdklab
2024-09-02 16:05 ` dpdklab
2024-09-02 16:07 ` dpdklab
2024-09-02 16:08 ` dpdklab
2024-09-02 16:36 ` dpdklab
2024-09-02 17:02 ` dpdklab
2024-09-02 17:36 ` dpdklab
2024-09-02 18:10 ` dpdklab
2024-09-02 18:45 ` dpdklab
2024-09-02 18:58 ` dpdklab
2024-09-18 20:56 ` dpdklab
2024-09-18 21:15 ` dpdklab
2024-09-18 21:28 ` dpdklab
2024-09-18 21:47 ` 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=66d5dacc.170a0220.3b4e91.1a06SMTPIN_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).