From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139856 [PATCH] [RFC,v3] net/af_packet: make stats reset
Date: Fri, 03 May 2024 13:25:42 -0700 (PDT) [thread overview]
Message-ID: <66354846.050a0220.ec167.e267SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240503154547.392069-1-ferruh.yigit@amd.com>
Test-Label: iol-unit-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139856
_Testing PASS_
Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Friday, May 03 2024 15:45:47
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:baa8e2c6b4d7ce289e891b9c96fb3193311c0f01
139856 --> testing pass
Test environment and result as below:
+----------------------+--------------+
| Environment | lpm_autotest |
+======================+==============+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------+--------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-167-generic
Compiler: gcc (Ubuntu 10.5.0-1ubuntu1~20.04) 10.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29909/
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-05-03 20:25 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240503154547.392069-1-ferruh.yigit@amd.com>
2024-05-03 15:19 ` |SUCCESS| pw139856 [RFC v3] net/af_packet: make stats reset reliable qemudev
2024-05-03 15:24 ` qemudev
2024-05-03 15:47 ` checkpatch
2024-05-03 19:49 ` |SUCCESS| pw139856 [PATCH] [RFC,v3] net/af_packet: make stats reset dpdklab
2024-05-03 19:51 ` dpdklab
2024-05-03 20:12 ` dpdklab
2024-05-03 20:13 ` dpdklab
2024-05-03 20:13 ` dpdklab
2024-05-03 20:14 ` dpdklab
2024-05-03 20:14 ` dpdklab
2024-05-03 20:15 ` dpdklab
2024-05-03 20:16 ` dpdklab
2024-05-03 20:18 ` dpdklab
2024-05-03 20:19 ` dpdklab
2024-05-03 20:19 ` dpdklab
2024-05-03 20:20 ` dpdklab
2024-05-03 20:20 ` dpdklab
2024-05-03 20:20 ` dpdklab
2024-05-03 20:20 ` dpdklab
2024-05-03 20:21 ` dpdklab
2024-05-03 20:21 ` dpdklab
2024-05-03 20:21 ` dpdklab
2024-05-03 20:21 ` dpdklab
2024-05-03 20:21 ` dpdklab
2024-05-03 20:22 ` dpdklab
2024-05-03 20:22 ` dpdklab
2024-05-03 20:22 ` dpdklab
2024-05-03 20:22 ` dpdklab
2024-05-03 20:22 ` dpdklab
2024-05-03 20:23 ` dpdklab
2024-05-03 20:23 ` dpdklab
2024-05-03 20:23 ` dpdklab
2024-05-03 20:23 ` dpdklab
2024-05-03 20:23 ` dpdklab
2024-05-03 20:23 ` dpdklab
2024-05-03 20:24 ` dpdklab
2024-05-03 20:24 ` dpdklab
2024-05-03 20:24 ` dpdklab
2024-05-03 20:24 ` dpdklab
2024-05-03 20:24 ` dpdklab
2024-05-03 20:24 ` dpdklab
2024-05-03 20:24 ` dpdklab
2024-05-03 20:25 ` dpdklab
2024-05-03 20:25 ` dpdklab
2024-05-03 20:25 ` dpdklab
2024-05-03 20:25 ` dpdklab
2024-05-03 20:25 ` dpdklab
2024-05-03 20:25 ` dpdklab
2024-05-03 20:25 ` dpdklab [this message]
2024-05-03 20:25 ` dpdklab
2024-05-03 20:27 ` dpdklab
2024-05-03 20:27 ` dpdklab
2024-05-03 20:27 ` dpdklab
2024-05-03 20:28 ` dpdklab
2024-05-03 20:31 ` dpdklab
2024-05-03 20:33 ` dpdklab
2024-05-03 20:35 ` dpdklab
2024-05-03 20:35 ` dpdklab
2024-05-03 20:37 ` dpdklab
2024-05-03 20:39 ` dpdklab
2024-05-03 20:39 ` dpdklab
2024-05-03 20:40 ` dpdklab
2024-05-03 20:41 ` dpdklab
2024-05-03 20:41 ` dpdklab
2024-05-03 20:42 ` dpdklab
2024-05-03 20:45 ` dpdklab
2024-05-03 20:46 ` dpdklab
2024-05-03 20:50 ` dpdklab
2024-05-03 20:54 ` dpdklab
2024-05-03 20:56 ` dpdklab
2024-05-03 21:06 ` dpdklab
2024-05-03 21:06 ` dpdklab
2024-05-03 21:14 ` dpdklab
2024-05-03 21:21 ` dpdklab
2024-05-03 21:21 ` dpdklab
2024-05-03 21:21 ` dpdklab
2024-05-03 21:25 ` dpdklab
2024-05-03 21:31 ` dpdklab
2024-05-03 21:37 ` dpdklab
2024-05-03 21:49 ` dpdklab
2024-05-03 21:51 ` dpdklab
2024-05-03 22:05 ` dpdklab
2024-05-04 5:51 ` dpdklab
2024-05-05 9:06 ` dpdklab
2024-05-05 9:18 ` dpdklab
2024-05-05 9:26 ` dpdklab
2024-05-05 9:27 ` dpdklab
2024-05-05 9:38 ` dpdklab
2024-05-06 12: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=66354846.050a0220.ec167.e267SMTPIN_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).