From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139645 [PATCH] event: fix warning from useless snprintf
Date: Wed, 24 Apr 2024 09:37:25 -0700 (PDT) [thread overview]
Message-ID: <66293545.810a0220.29d52.ea0cSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240424034541.134335-1-stephen@networkplumber.org>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139645
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, April 24 2024 03:45:40
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139645 --> testing pass
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
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/29848/
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-04-24 16:37 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240424034541.134335-1-stephen@networkplumber.org>
2024-04-24 3:20 ` qemudev
2024-04-24 3:24 ` qemudev
2024-04-24 3:46 ` |WARNING| " checkpatch
2024-04-24 4:45 ` |SUCCESS| " 0-day Robot
2024-04-24 14:24 ` dpdklab
2024-04-24 14:35 ` dpdklab
2024-04-24 14:37 ` dpdklab
2024-04-24 14:37 ` dpdklab
2024-04-24 14:39 ` dpdklab
2024-04-24 14:39 ` dpdklab
2024-04-24 14:40 ` dpdklab
2024-04-24 14:41 ` dpdklab
2024-04-24 14:42 ` dpdklab
2024-04-24 14:43 ` dpdklab
2024-04-24 14:52 ` dpdklab
2024-04-24 14:53 ` dpdklab
2024-04-24 14:53 ` dpdklab
2024-04-24 14:53 ` dpdklab
2024-04-24 14:54 ` dpdklab
2024-04-24 14:54 ` dpdklab
2024-04-24 14:54 ` dpdklab
2024-04-24 14:55 ` dpdklab
2024-04-24 14:55 ` dpdklab
2024-04-24 14:55 ` dpdklab
2024-04-24 14:55 ` dpdklab
2024-04-24 14:56 ` dpdklab
2024-04-24 14:56 ` dpdklab
2024-04-24 14:57 ` dpdklab
2024-04-24 14:58 ` dpdklab
2024-04-24 14:59 ` dpdklab
2024-04-24 15:00 ` dpdklab
2024-04-24 15:02 ` dpdklab
2024-04-24 15:02 ` dpdklab
2024-04-24 15:03 ` dpdklab
2024-04-24 15:03 ` dpdklab
2024-04-24 15:04 ` dpdklab
2024-04-24 15:04 ` dpdklab
2024-04-24 15:05 ` dpdklab
2024-04-24 15:05 ` dpdklab
2024-04-24 15:05 ` dpdklab
2024-04-24 15:07 ` dpdklab
2024-04-24 15:07 ` dpdklab
2024-04-24 15:07 ` dpdklab
2024-04-24 15:07 ` dpdklab
2024-04-24 15:08 ` dpdklab
2024-04-24 15:08 ` dpdklab
2024-04-24 15:08 ` dpdklab
2024-04-24 15:08 ` dpdklab
2024-04-24 15:11 ` dpdklab
2024-04-24 15:11 ` dpdklab
2024-04-24 15:11 ` dpdklab
2024-04-24 15:11 ` dpdklab
2024-04-24 15:11 ` dpdklab
2024-04-24 15:12 ` dpdklab
2024-04-24 15:14 ` dpdklab
2024-04-24 15:14 ` dpdklab
2024-04-24 15:15 ` dpdklab
2024-04-24 15:16 ` dpdklab
2024-04-24 15:17 ` dpdklab
2024-04-24 15:17 ` dpdklab
2024-04-24 15:17 ` dpdklab
2024-04-24 15:18 ` dpdklab
2024-04-24 15:18 ` dpdklab
2024-04-24 15:19 ` dpdklab
2024-04-24 15:19 ` dpdklab
2024-04-24 15:20 ` dpdklab
2024-04-24 15:22 ` dpdklab
2024-04-24 15:23 ` dpdklab
2024-04-24 15:24 ` dpdklab
2024-04-24 15:24 ` dpdklab
2024-04-24 15:25 ` dpdklab
2024-04-24 15:25 ` dpdklab
2024-04-24 15:25 ` dpdklab
2024-04-24 15:25 ` dpdklab
2024-04-24 15:25 ` dpdklab
2024-04-24 15:26 ` dpdklab
2024-04-24 15:28 ` dpdklab
2024-04-24 15:29 ` dpdklab
2024-04-24 15:30 ` dpdklab
2024-04-24 15:32 ` dpdklab
2024-04-24 15:33 ` dpdklab
2024-04-24 15:35 ` dpdklab
2024-04-24 15:42 ` dpdklab
2024-04-24 15:43 ` dpdklab
2024-04-24 15:46 ` dpdklab
2024-04-24 15:48 ` dpdklab
2024-04-24 15:52 ` dpdklab
2024-04-24 15:56 ` dpdklab
2024-04-24 16:22 ` dpdklab
2024-04-24 16:37 ` dpdklab [this message]
2024-04-24 17:45 ` dpdklab
2024-04-24 17:47 ` 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=66293545.810a0220.29d52.ea0cSMTPIN_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).