From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143759 [PATCH] fib: network byte order IPv4 lookup
Date: Sat, 07 Sep 2024 02:05:18 -0700 (PDT) [thread overview]
Message-ID: <66dc174e.d40a0220.33e5cd.27d7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240906170649.1325254-1-vladimir.medvedkin@intel.com>
Test-Label: iol-broadcom-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/143759
_Functional Testing PASS_
Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Friday, September 06 2024 17:06:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
143759 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#179120
Test environment and result as below:
Ubuntu 22.04 ARM
Kernel: 5.15.83+
Compiler: gcc 11.4.0
NIC: Arm Broadcom Inc. brcm_57414 25000 Mbps
Aggregate Results by Test Suite
+------------+--------+
| Test Suite | Result |
+============+========+
| scatter | PASS |
+------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30950/
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-07 9:05 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240906170649.1325254-1-vladimir.medvedkin@intel.com>
2024-09-06 16:51 ` qemudev
2024-09-06 16:55 ` qemudev
2024-09-06 17:07 ` checkpatch
2024-09-06 17:44 ` |FAILURE| " 0-day Robot
2024-09-06 21:56 ` |SUCCESS| " dpdklab
2024-09-06 22:10 ` dpdklab
2024-09-06 22:13 ` dpdklab
2024-09-06 22:13 ` |PENDING| " dpdklab
2024-09-06 22:26 ` |SUCCESS| " dpdklab
2024-09-06 22:27 ` dpdklab
2024-09-06 22:32 ` dpdklab
2024-09-06 23:00 ` dpdklab
2024-09-06 23:00 ` dpdklab
2024-09-06 23:16 ` |PENDING| " dpdklab
2024-09-06 23:35 ` |SUCCESS| " dpdklab
2024-09-06 23:42 ` |PENDING| " dpdklab
2024-09-06 23:49 ` dpdklab
2024-09-06 23:59 ` dpdklab
2024-09-07 0:09 ` |SUCCESS| " dpdklab
2024-09-07 1:32 ` |FAILURE| " dpdklab
2024-09-07 1:34 ` |WARNING| " dpdklab
2024-09-07 2:24 ` |FAILURE| " dpdklab
2024-09-07 3:04 ` dpdklab
2024-09-07 4:31 ` |SUCCESS| " dpdklab
2024-09-07 4:48 ` |FAILURE| " dpdklab
2024-09-07 4:48 ` dpdklab
2024-09-07 5:11 ` |WARNING| " dpdklab
2024-09-07 5:17 ` |SUCCESS| " dpdklab
2024-09-07 5:35 ` |WARNING| " dpdklab
2024-09-07 9:00 ` |SUCCESS| " dpdklab
2024-09-07 9:05 ` dpdklab [this message]
2024-09-07 9:24 ` dpdklab
2024-09-07 9:29 ` dpdklab
2024-09-07 9:37 ` dpdklab
2024-09-07 9:42 ` dpdklab
2024-09-07 9:47 ` dpdklab
2024-09-07 9:52 ` dpdklab
2024-09-07 10:34 ` dpdklab
2024-09-07 11:00 ` dpdklab
2024-09-07 13:44 ` |FAILURE| " dpdklab
2024-09-07 14:04 ` dpdklab
2024-09-07 14:30 ` |WARNING| " dpdklab
2024-09-07 14:39 ` dpdklab
2024-09-07 14:46 ` |FAILURE| " dpdklab
2024-09-07 14:46 ` dpdklab
2024-09-07 14:48 ` dpdklab
2024-09-07 14:49 ` dpdklab
2024-09-07 14:50 ` dpdklab
2024-09-07 14:52 ` dpdklab
2024-09-07 14:52 ` dpdklab
2024-09-07 14:54 ` dpdklab
2024-09-07 14:54 ` dpdklab
2024-09-07 14:55 ` dpdklab
2024-09-07 14:56 ` dpdklab
2024-09-07 14:57 ` dpdklab
2024-09-07 14:57 ` dpdklab
2024-09-07 14:57 ` dpdklab
2024-09-07 14:59 ` dpdklab
2024-09-07 14:59 ` dpdklab
2024-09-07 15:00 ` dpdklab
2024-09-07 15:00 ` dpdklab
2024-09-07 15:01 ` dpdklab
2024-09-07 15:02 ` dpdklab
2024-09-07 15:03 ` dpdklab
2024-09-07 15:04 ` dpdklab
2024-09-07 15:04 ` dpdklab
2024-09-07 15:04 ` dpdklab
2024-09-07 15:05 ` dpdklab
2024-09-07 15:05 ` dpdklab
2024-09-07 15:07 ` dpdklab
2024-09-07 15:38 ` dpdklab
2024-09-07 16:07 ` dpdklab
2024-09-07 16:09 ` dpdklab
2024-09-07 16:09 ` dpdklab
2024-09-08 10:38 ` |SUCCESS| " dpdklab
2024-09-08 11:06 ` dpdklab
2024-09-17 2:33 ` dpdklab
2024-09-17 2:52 ` dpdklab
2024-09-17 3:03 ` 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=66dc174e.d40a0220.33e5cd.27d7SMTPIN_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).