From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143208 [PATCH] [RFC] table: report victim replace stats
Date: Mon, 19 Aug 2024 00:24:38 -0700 (PDT) [thread overview]
Message-ID: <66c2f336.050a0220.158e9a.fa20SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240819052330.46122-1-vojanec@cesnet.cz>
Test-Label: iol-marvell-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143208
_Functional Testing PASS_
Submitter: Kamil Vojanec <vojanec@cesnet.cz>
Date: Monday, August 19 2024 05:23:30
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143208 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#175831
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 |
+-----------------+--------+
| coremask | PASS |
+-----------------+--------+
| ipv4_reassembly | PASS |
+-----------------+--------+
| l2fwd | PASS |
+-----------------+--------+
| rxtx_callbacks | PASS |
+-----------------+--------+
| tso | PASS |
+-----------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30805/
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-19 7:24 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240819052330.46122-1-vojanec@cesnet.cz>
2024-08-19 4:56 ` |SUCCESS| pw143208 [RFC] table: report victim replace stats in LRU tables qemudev
2024-08-19 5:01 ` qemudev
2024-08-19 5:25 ` checkpatch
2024-08-19 6:22 ` 0-day Robot
2024-08-19 7:03 ` |PENDING| pw143208 [PATCH] [RFC] table: report victim replace stats dpdklab
2024-08-19 7:11 ` |SUCCESS| " dpdklab
2024-08-19 7:15 ` dpdklab
2024-08-19 7:19 ` dpdklab
2024-08-19 7:19 ` dpdklab
2024-08-19 7:20 ` dpdklab
2024-08-19 7:22 ` dpdklab
2024-08-19 7:23 ` |PENDING| " dpdklab
2024-08-19 7:23 ` |SUCCESS| " dpdklab
2024-08-19 7:23 ` dpdklab
2024-08-19 7:24 ` dpdklab [this message]
2024-08-19 7:24 ` dpdklab
2024-08-19 7:30 ` dpdklab
2024-08-19 7:32 ` dpdklab
2024-08-19 7:33 ` dpdklab
2024-08-19 7:33 ` dpdklab
2024-08-19 7:34 ` dpdklab
2024-08-19 7:35 ` dpdklab
2024-08-19 7:35 ` dpdklab
2024-08-19 7:37 ` dpdklab
2024-08-19 7:42 ` dpdklab
2024-08-19 7:43 ` dpdklab
2024-08-19 7:45 ` dpdklab
2024-08-19 7:46 ` dpdklab
2024-08-19 7:47 ` dpdklab
2024-08-19 7:49 ` |PENDING| " dpdklab
2024-08-19 7:49 ` |SUCCESS| " dpdklab
2024-08-19 7:55 ` dpdklab
2024-08-19 8:02 ` dpdklab
2024-08-19 8:04 ` dpdklab
2024-08-19 8:06 ` dpdklab
2024-08-19 8:08 ` dpdklab
2024-08-19 8:13 ` dpdklab
2024-08-19 8:14 ` dpdklab
2024-08-19 8:22 ` dpdklab
2024-08-19 8:29 ` dpdklab
2024-08-19 8:34 ` dpdklab
2024-08-19 8:40 ` dpdklab
2024-08-19 8:45 ` dpdklab
2024-08-19 8:53 ` dpdklab
2024-08-19 9:21 ` dpdklab
2024-08-19 9:24 ` dpdklab
2024-08-19 9:26 ` dpdklab
2024-08-19 9:26 ` dpdklab
2024-08-19 9:30 ` dpdklab
2024-08-19 10:18 ` dpdklab
2024-08-19 11:38 ` dpdklab
2024-08-19 14:04 ` 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=66c2f336.050a0220.158e9a.fa20SMTPIN_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).