From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw145777 [PATCH] [v4] fib: network byte order IPv4 lookup
Date: Sun, 13 Oct 2024 12:31:44 -0700 (PDT) [thread overview]
Message-ID: <670c2020.050a0220.3c6ac1.e1e4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241011175701.116371-1-vladimir.medvedkin@intel.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/145777
_Testing PASS_
Submitter: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Date: Friday, October 11 2024 17:57:01
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:98613d32e3dac58d685f4f236cf8cc9733abaaf3
145777 --> testing pass
Upstream job id: Generic-VM-DPDK-Compile-Meson#30232
Test environment and result as below:
+--------------+--------------------+
| Environment | dpdk_meson_compile |
+==============+====================+
| FreeBSD 14.1 | PASS |
+--------------+--------------------+
FreeBSD 14.1
Kernel: 14.1-RELEASE-p3
Compiler: clang 18.1.5
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31441/
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-10-13 19:31 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241011175701.116371-1-vladimir.medvedkin@intel.com>
2024-10-11 17:46 ` |FAILURE| pw145777 [PATCH v4] " qemudev
2024-10-11 17:57 ` |SUCCESS| " checkpatch
2024-10-11 18:42 ` |FAILURE| " 0-day Robot
2024-10-13 11:42 ` |FAILURE| pw145777 [PATCH] [v4] " dpdklab
2024-10-13 12:04 ` |SUCCESS| " dpdklab
2024-10-13 12:17 ` |FAILURE| " dpdklab
2024-10-13 12:19 ` dpdklab
2024-10-13 12:19 ` dpdklab
2024-10-13 12:22 ` |WARNING| " dpdklab
2024-10-13 12:37 ` |SUCCESS| " dpdklab
2024-10-13 13:53 ` |WARNING| " dpdklab
2024-10-13 19:31 ` dpdklab [this message]
2024-10-13 19:44 ` |PENDING| " dpdklab
2024-10-13 20:01 ` |FAILURE| " dpdklab
2024-10-13 20:13 ` |SUCCESS| " dpdklab
2024-10-13 20:32 ` |FAILURE| " dpdklab
2024-10-13 20:52 ` dpdklab
2024-10-13 20:53 ` dpdklab
2024-10-13 20:58 ` dpdklab
2024-10-13 20:59 ` dpdklab
2024-10-13 21:01 ` dpdklab
2024-10-13 21:01 ` dpdklab
2024-10-13 21:02 ` dpdklab
2024-10-13 21:04 ` dpdklab
2024-10-13 21:05 ` dpdklab
2024-10-13 21:05 ` dpdklab
2024-10-13 21:05 ` dpdklab
2024-10-13 21:06 ` dpdklab
2024-10-13 21:08 ` dpdklab
2024-10-13 21:08 ` dpdklab
2024-10-13 21:09 ` dpdklab
2024-10-13 21:09 ` dpdklab
2024-10-13 21:09 ` dpdklab
2024-10-13 21:10 ` dpdklab
2024-10-13 21:10 ` dpdklab
2024-10-13 21:11 ` dpdklab
2024-10-13 21:11 ` dpdklab
2024-10-13 21:13 ` dpdklab
2024-10-13 21:14 ` dpdklab
2024-10-13 21:15 ` dpdklab
2024-10-13 21:16 ` dpdklab
2024-10-13 21:16 ` dpdklab
2024-10-13 21:17 ` dpdklab
2024-10-13 21:17 ` dpdklab
2024-10-13 21:17 ` dpdklab
2024-10-13 21:18 ` dpdklab
2024-10-13 21:37 ` dpdklab
2024-10-13 21:37 ` dpdklab
2024-10-13 23:12 ` dpdklab
2024-10-13 23:20 ` dpdklab
2024-10-13 23:29 ` |SUCCESS| " 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=670c2020.050a0220.3c6ac1.e1e4SMTPIN_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).