From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw142740 [PATCH] examples/l3fwd: fix read beyond array bon
Date: Fri, 26 Jul 2024 15:12:42 -0700 (PDT) [thread overview]
Message-ID: <66a41f5a.0d0a0220.261e23.263aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240726194302.920-1-konstantin.v.ananyev@yandex.ru>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/142740
_Testing PASS_
Submitter: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Date: Friday, July 26 2024 19:43:02
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:82c47f005b9a0a1e3a649664b7713443d18abe43
142740 --> testing pass
Upstream job id: ACVP-FIPS-testing#6427
Test environment and result as below:
+--------------------+----------------------+----------------------+
| Environment | compressdev_zlib_pmd | dpdk_fips_validation |
+====================+======================+======================+
| Ubuntu 22.04 (ARM) | PASS | SKIPPED |
+--------------------+----------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+--------------------+----------------------+----------------------+
| Ubuntu 20.04 | SKIPPED | PASS |
+--------------------+----------------------+----------------------+
Ubuntu 22.04 (ARM)
Kernel: 5.15.0-97-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30636/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2024-07-26 22:12 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240726194302.920-1-konstantin.v.ananyev@yandex.ru>
2024-07-26 19:16 ` |SUCCESS| pw142740 [PATCH] examples/l3fwd: fix read beyond array bondaries qemudev
2024-07-26 19:21 ` qemudev
2024-07-26 19:44 ` |WARNING| " checkpatch
2024-07-26 20:16 ` |PENDING| pw142740 [PATCH] examples/l3fwd: fix read beyond array bon dpdklab
2024-07-26 20:17 ` |SUCCESS| " dpdklab
2024-07-26 20:19 ` |PENDING| " dpdklab
2024-07-26 20:22 ` |SUCCESS| " dpdklab
2024-07-26 20:25 ` |PENDING| " dpdklab
2024-07-26 20:25 ` |SUCCESS| " dpdklab
2024-07-26 20:25 ` dpdklab
2024-07-26 20:26 ` |PENDING| " dpdklab
2024-07-26 20:26 ` dpdklab
2024-07-26 20:29 ` dpdklab
2024-07-26 20:30 ` dpdklab
2024-07-26 20:31 ` dpdklab
2024-07-26 20:32 ` dpdklab
2024-07-26 20:32 ` dpdklab
2024-07-26 20:32 ` dpdklab
2024-07-26 20:34 ` |SUCCESS| " dpdklab
2024-07-26 20:34 ` |PENDING| " dpdklab
2024-07-26 20:34 ` dpdklab
2024-07-26 20:34 ` dpdklab
2024-07-26 20:35 ` dpdklab
2024-07-26 20:35 ` dpdklab
2024-07-26 20:37 ` dpdklab
2024-07-26 20:37 ` dpdklab
2024-07-26 20:37 ` dpdklab
2024-07-26 20:38 ` dpdklab
2024-07-26 20:38 ` dpdklab
2024-07-26 20:39 ` dpdklab
2024-07-26 20:39 ` dpdklab
2024-07-26 20:39 ` dpdklab
2024-07-26 20:40 ` |SUCCESS| " dpdklab
2024-07-26 20:40 ` |PENDING| " dpdklab
2024-07-26 20:40 ` dpdklab
2024-07-26 20:41 ` dpdklab
2024-07-26 20:42 ` dpdklab
2024-07-26 20:43 ` |SUCCESS| pw142740 [PATCH] examples/l3fwd: fix read beyond array bondaries 0-day Robot
2024-07-26 20:43 ` |SUCCESS| pw142740 [PATCH] examples/l3fwd: fix read beyond array bon dpdklab
2024-07-26 20:43 ` |PENDING| " dpdklab
2024-07-26 20:44 ` |SUCCESS| " dpdklab
2024-07-26 20:44 ` |PENDING| " dpdklab
2024-07-26 20:45 ` |SUCCESS| " dpdklab
2024-07-26 20:46 ` dpdklab
2024-07-26 20:46 ` |PENDING| " dpdklab
2024-07-26 20:47 ` dpdklab
2024-07-26 20:47 ` dpdklab
2024-07-26 20:47 ` dpdklab
2024-07-26 20:48 ` dpdklab
2024-07-26 20:48 ` dpdklab
2024-07-26 20:48 ` dpdklab
2024-07-26 20:48 ` dpdklab
2024-07-26 20:48 ` dpdklab
2024-07-26 20:49 ` dpdklab
2024-07-26 20:51 ` dpdklab
2024-07-26 20:51 ` dpdklab
2024-07-26 20:53 ` dpdklab
2024-07-26 20:54 ` dpdklab
2024-07-26 20:56 ` dpdklab
2024-07-26 20:56 ` dpdklab
2024-07-26 20:57 ` dpdklab
2024-07-26 20:58 ` dpdklab
2024-07-26 21:00 ` dpdklab
2024-07-26 21:01 ` dpdklab
2024-07-26 21:02 ` dpdklab
2024-07-26 21:02 ` dpdklab
2024-07-26 21:02 ` dpdklab
2024-07-26 21:03 ` dpdklab
2024-07-26 21:03 ` |SUCCESS| " dpdklab
2024-07-26 21:04 ` |PENDING| " dpdklab
2024-07-26 21:04 ` dpdklab
2024-07-26 21:05 ` dpdklab
2024-07-26 21:06 ` dpdklab
2024-07-26 21:07 ` dpdklab
2024-07-26 21:08 ` dpdklab
2024-07-26 21:09 ` dpdklab
2024-07-26 21:11 ` dpdklab
2024-07-26 21:11 ` dpdklab
2024-07-26 21:11 ` dpdklab
2024-07-26 21:12 ` |SUCCESS| " dpdklab
2024-07-26 21:12 ` |PENDING| " dpdklab
2024-07-26 21:13 ` dpdklab
2024-07-26 21:14 ` dpdklab
2024-07-26 21:14 ` |SUCCESS| " dpdklab
2024-07-26 21:15 ` |PENDING| " dpdklab
2024-07-26 21:16 ` dpdklab
2024-07-26 21:17 ` dpdklab
2024-07-26 21:17 ` dpdklab
2024-07-26 21:18 ` |SUCCESS| " dpdklab
2024-07-26 21:19 ` |PENDING| " dpdklab
2024-07-26 21:21 ` dpdklab
2024-07-26 21:22 ` dpdklab
2024-07-26 21:22 ` dpdklab
2024-07-26 21:24 ` dpdklab
2024-07-26 21:25 ` dpdklab
2024-07-26 21:26 ` dpdklab
2024-07-26 21:27 ` dpdklab
2024-07-26 21:28 ` dpdklab
2024-07-26 21:28 ` dpdklab
2024-07-26 21:29 ` dpdklab
2024-07-26 21:30 ` dpdklab
2024-07-26 21:31 ` dpdklab
2024-07-26 21:31 ` dpdklab
2024-07-26 21:34 ` |SUCCESS| " dpdklab
2024-07-26 21:39 ` |PENDING| " dpdklab
2024-07-26 21:41 ` dpdklab
2024-07-26 21:43 ` dpdklab
2024-07-26 21:45 ` |SUCCESS| " dpdklab
2024-07-26 21:45 ` dpdklab
2024-07-26 21:46 ` |PENDING| " dpdklab
2024-07-26 21:46 ` |SUCCESS| " dpdklab
2024-07-26 21:58 ` |PENDING| " dpdklab
2024-07-26 22:04 ` |SUCCESS| " dpdklab
2024-07-26 22:12 ` dpdklab [this message]
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=66a41f5a.0d0a0220.261e23.263aSMTPIN_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).