From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw139111-139112 [PATCH] [v1,3/3] test/bbdev: update for qu
Date: Thu, 04 Apr 2024 16:23:32 -0700 (PDT) [thread overview]
Message-ID: <660f3674.170a0220.a6d88.0bceSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240404210447.1915517-4-nicolas.chautru@intel.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/139112
_Testing PASS_
Submitter: Nicolas Chautru <nicolas.chautru@intel.com>
Date: Thursday, April 04 2024 21:04:47
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:98b4ecb4e4d73e93fdfa53f552b48d71104b445f
139111-139112 --> 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/29718/
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-04 23:23 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240404210447.1915517-4-nicolas.chautru@intel.com>
2024-04-04 20:41 ` |SUCCESS| pw139111-139112 [PATCH v1 3/3] test/bbdev: update for queue stats qemudev
2024-04-04 20:45 ` qemudev
2024-04-04 21:05 ` |SUCCESS| pw139112 " checkpatch
2024-04-04 21:53 ` |SUCCESS| pw139111-139112 [PATCH] [v1,3/3] test/bbdev: update for qu dpdklab
2024-04-04 21:54 ` dpdklab
2024-04-04 21:55 ` dpdklab
2024-04-04 21:55 ` dpdklab
2024-04-04 21:56 ` dpdklab
2024-04-04 21:56 ` dpdklab
2024-04-04 21:57 ` dpdklab
2024-04-04 21:57 ` dpdklab
2024-04-04 21:57 ` dpdklab
2024-04-04 21:58 ` dpdklab
2024-04-04 22:01 ` dpdklab
2024-04-04 22:02 ` |WARNING| " dpdklab
2024-04-04 22:04 ` |FAILURE| pw139112 [PATCH v1 3/3] test/bbdev: update for queue stats 0-day Robot
2024-04-04 22:07 ` |WARNING| pw139111-139112 [PATCH] [v1,3/3] test/bbdev: update for qu dpdklab
2024-04-04 22:08 ` |SUCCESS| " dpdklab
2024-04-04 22:09 ` |WARNING| " dpdklab
2024-04-04 22:10 ` |SUCCESS| " dpdklab
2024-04-04 22:10 ` |FAILURE| " dpdklab
2024-04-04 22:11 ` |WARNING| " dpdklab
2024-04-04 22:11 ` dpdklab
2024-04-04 22:12 ` |SUCCESS| " dpdklab
2024-04-04 22:12 ` dpdklab
2024-04-04 22:13 ` dpdklab
2024-04-04 22:13 ` |WARNING| " dpdklab
2024-04-04 22:13 ` |FAILURE| " dpdklab
2024-04-04 22:14 ` |WARNING| " dpdklab
2024-04-04 22:14 ` dpdklab
2024-04-04 22:14 ` dpdklab
2024-04-04 22:15 ` dpdklab
2024-04-04 22:15 ` |SUCCESS| " dpdklab
2024-04-04 22:15 ` dpdklab
2024-04-04 22:15 ` |WARNING| " dpdklab
2024-04-04 22:16 ` |FAILURE| " dpdklab
2024-04-04 22:16 ` |WARNING| " dpdklab
2024-04-04 22:16 ` |FAILURE| " dpdklab
2024-04-04 22:16 ` |SUCCESS| " dpdklab
2024-04-04 22:20 ` |FAILURE| " dpdklab
2024-04-04 22:21 ` |SUCCESS| " dpdklab
2024-04-04 22:22 ` |FAILURE| " dpdklab
2024-04-04 22:22 ` |SUCCESS| " dpdklab
2024-04-04 22:23 ` dpdklab
2024-04-04 22:24 ` dpdklab
2024-04-04 22:24 ` |FAILURE| " dpdklab
2024-04-04 22:27 ` |SUCCESS| " dpdklab
2024-04-04 22:27 ` dpdklab
2024-04-04 22:27 ` |FAILURE| " dpdklab
2024-04-04 22:29 ` |SUCCESS| " dpdklab
2024-04-04 22:29 ` |FAILURE| " dpdklab
2024-04-04 22:32 ` |SUCCESS| " dpdklab
2024-04-04 22:33 ` dpdklab
2024-04-04 22:33 ` |FAILURE| " dpdklab
2024-04-04 22:34 ` |SUCCESS| " dpdklab
2024-04-04 22:34 ` |FAILURE| " dpdklab
2024-04-04 22:35 ` dpdklab
2024-04-04 22:36 ` |SUCCESS| " dpdklab
2024-04-04 22:37 ` |FAILURE| " dpdklab
2024-04-04 22:37 ` |SUCCESS| " dpdklab
2024-04-04 22:38 ` |FAILURE| " dpdklab
2024-04-04 22:39 ` |SUCCESS| " dpdklab
2024-04-04 22:45 ` |FAILURE| " dpdklab
2024-04-04 22:47 ` |SUCCESS| " dpdklab
2024-04-04 22:53 ` dpdklab
2024-04-04 23:01 ` dpdklab
2024-04-04 23:23 ` dpdklab [this message]
2024-04-04 23:37 ` dpdklab
2024-04-04 23:37 ` dpdklab
2024-04-04 23:40 ` dpdklab
2024-04-04 23:46 ` dpdklab
2024-04-04 23:59 ` dpdklab
2024-04-05 0:00 ` dpdklab
2024-04-05 0:03 ` dpdklab
2024-04-05 0:04 ` dpdklab
2024-04-05 0:07 ` dpdklab
2024-04-05 0:08 ` dpdklab
2024-04-05 0:10 ` dpdklab
2024-04-05 0:11 ` dpdklab
2024-04-05 0:13 ` dpdklab
2024-04-05 0:15 ` dpdklab
2024-04-05 0:30 ` dpdklab
2024-04-05 0:33 ` dpdklab
2024-04-05 0:38 ` dpdklab
2024-04-05 0:38 ` dpdklab
2024-04-05 0:41 ` dpdklab
2024-04-05 0:43 ` dpdklab
2024-04-05 0:58 ` dpdklab
2024-04-05 1:05 ` dpdklab
2024-04-05 1:06 ` dpdklab
2024-04-05 1:14 ` dpdklab
2024-04-05 1:38 ` dpdklab
2024-04-05 1:44 ` 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=660f3674.170a0220.a6d88.0bceSMTPIN_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).