From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw128889 [PATCH] [v3] bitmap: add scan from offset functio
Date: Wed, 21 Jun 2023 14:36:56 -0700 (PDT) [thread overview]
Message-ID: <64936d78.050a0220.50c4a.b544SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/128889
_Testing PASS_
Submitter: Volodymyr Fialko <vfialko@marvell.com>
Date: Wednesday, June 21 2023 10:01:05
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4645ed709d36bab64fbf2b8cff12054d39398af9
128889 --> testing pass
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26768/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-06-21 21:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 21:36 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-21 21:37 dpdklab
2023-06-21 20:32 dpdklab
2023-06-21 20:28 dpdklab
2023-06-21 20:11 dpdklab
2023-06-21 13:18 dpdklab
2023-06-21 13:10 dpdklab
2023-06-21 13:03 dpdklab
2023-06-21 12:58 dpdklab
2023-06-21 12:51 dpdklab
2023-06-21 12:49 dpdklab
2023-06-21 12:49 dpdklab
2023-06-21 12:41 dpdklab
2023-06-21 12:40 dpdklab
2023-06-21 12:31 dpdklab
2023-06-21 12:31 dpdklab
2023-06-21 12:15 dpdklab
2023-06-21 11:42 dpdklab
2023-06-21 11:40 dpdklab
2023-06-21 11:36 dpdklab
2023-06-21 11:35 dpdklab
2023-06-21 11:35 dpdklab
2023-06-21 11:29 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=64936d78.050a0220.50c4a.b544SMTPIN_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).