From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139083 [PATCH] doc: update required Mingw version
Date: Wed, 03 Apr 2024 13:45:18 -0700 (PDT) [thread overview]
Message-ID: <660dbfde.050a0220.e5403.8265SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240403162851.437218-1-stephen@networkplumber.org>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139083
_Testing PASS_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Wednesday, April 03 2024 16:28:51
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139083 --> 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/29706/
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-03 20:45 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240403162851.437218-1-stephen@networkplumber.org>
2024-04-03 16:09 ` qemudev
2024-04-03 16:13 ` qemudev
2024-04-03 16:29 ` checkpatch
2024-04-03 17:45 ` 0-day Robot
2024-04-03 17:59 ` dpdklab
2024-04-03 18:01 ` dpdklab
2024-04-03 18:11 ` dpdklab
2024-04-03 18:12 ` dpdklab
2024-04-03 18:15 ` dpdklab
2024-04-03 18:15 ` dpdklab
2024-04-03 18:16 ` dpdklab
2024-04-03 18:16 ` dpdklab
2024-04-03 18:20 ` dpdklab
2024-04-03 18:21 ` dpdklab
2024-04-03 18:34 ` dpdklab
2024-04-03 18:35 ` dpdklab
2024-04-03 18:36 ` dpdklab
2024-04-03 18:36 ` dpdklab
2024-04-03 18:36 ` dpdklab
2024-04-03 18:37 ` dpdklab
2024-04-03 18:39 ` dpdklab
2024-04-03 18:40 ` dpdklab
2024-04-03 18:42 ` dpdklab
2024-04-03 18:42 ` dpdklab
2024-04-03 18:44 ` dpdklab
2024-04-03 18:46 ` dpdklab
2024-04-03 18:58 ` dpdklab
2024-04-03 18:58 ` dpdklab
2024-04-03 19:01 ` dpdklab
2024-04-03 19:02 ` dpdklab
2024-04-03 19:03 ` dpdklab
2024-04-03 19:04 ` dpdklab
2024-04-03 19:08 ` dpdklab
2024-04-03 19:26 ` dpdklab
2024-04-03 19:29 ` dpdklab
2024-04-03 19:30 ` dpdklab
2024-04-03 19:40 ` dpdklab
2024-04-03 19:42 ` dpdklab
2024-04-03 19:42 ` dpdklab
2024-04-03 19:44 ` dpdklab
2024-04-03 19:44 ` dpdklab
2024-04-03 19:44 ` dpdklab
2024-04-03 19:45 ` dpdklab
2024-04-03 19:45 ` dpdklab
2024-04-03 19:45 ` dpdklab
2024-04-03 19:46 ` dpdklab
2024-04-03 19:46 ` dpdklab
2024-04-03 19:47 ` dpdklab
2024-04-03 19:47 ` dpdklab
2024-04-03 19:47 ` dpdklab
2024-04-03 19:48 ` dpdklab
2024-04-03 19:48 ` dpdklab
2024-04-03 19:49 ` dpdklab
2024-04-03 19:49 ` dpdklab
2024-04-03 19:50 ` dpdklab
2024-04-03 19:50 ` dpdklab
2024-04-03 19:51 ` dpdklab
2024-04-03 19:51 ` dpdklab
2024-04-03 19:51 ` dpdklab
2024-04-03 19:51 ` dpdklab
2024-04-03 19:52 ` dpdklab
2024-04-03 19:53 ` dpdklab
2024-04-03 19:54 ` dpdklab
2024-04-03 19:54 ` dpdklab
2024-04-03 19:55 ` dpdklab
2024-04-03 19:55 ` dpdklab
2024-04-03 19:55 ` dpdklab
2024-04-03 19:56 ` dpdklab
2024-04-03 19:56 ` dpdklab
2024-04-03 19:56 ` dpdklab
2024-04-03 19:57 ` dpdklab
2024-04-03 19:57 ` dpdklab
2024-04-03 19:57 ` dpdklab
2024-04-03 20:01 ` dpdklab
2024-04-03 20:05 ` dpdklab
2024-04-03 20:15 ` dpdklab
2024-04-03 20:45 ` dpdklab [this message]
2024-04-03 20:56 ` dpdklab
2024-04-03 21:32 ` dpdklab
2024-04-03 22:03 ` dpdklab
2024-04-03 22:05 ` dpdklab
2024-04-04 0:01 ` dpdklab
2024-04-04 0:56 ` dpdklab
2024-04-04 9:27 ` dpdklab
2024-04-04 9:31 ` dpdklab
2024-04-04 9:35 ` dpdklab
2024-04-04 9:39 ` dpdklab
2024-04-04 10:06 ` 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=660dbfde.050a0220.e5403.8265SMTPIN_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).