From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135928 [PATCH] net/iavf: fix application reset callback
Date: Thu, 18 Jan 2024 02:55:34 -0800 (PST) [thread overview]
Message-ID: <65a903a6.630a0220.e5c65.4e32SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135928
_Testing PASS_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Wednesday, January 17 2024 11:54:10
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:4e7732d6c4c64514dc26c3cc0203d19851b5f5aa
135928 --> testing pass
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28883/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-18 10:55 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 10:55 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-18 4:19 dpdklab
2024-01-18 3:46 dpdklab
2024-01-18 3:41 dpdklab
2024-01-18 3:40 dpdklab
2024-01-18 3:40 dpdklab
2024-01-18 3:39 dpdklab
2024-01-18 3:39 dpdklab
2024-01-18 3:27 dpdklab
2024-01-18 3:19 dpdklab
2024-01-18 3:16 dpdklab
2024-01-18 3:14 dpdklab
2024-01-18 3:14 dpdklab
2024-01-18 3:14 dpdklab
2024-01-18 3:06 dpdklab
2024-01-18 3:06 dpdklab
2024-01-18 3:05 dpdklab
2024-01-18 3:05 dpdklab
2024-01-18 3:05 dpdklab
2024-01-18 3:03 dpdklab
2024-01-18 3:03 dpdklab
2024-01-18 3:02 dpdklab
2024-01-18 2:58 dpdklab
2024-01-18 2:56 dpdklab
2024-01-18 2:55 dpdklab
2024-01-18 2:55 dpdklab
2024-01-18 2:52 dpdklab
2024-01-18 2:51 dpdklab
2024-01-18 2:51 dpdklab
2024-01-18 2:51 dpdklab
2024-01-18 2:50 dpdklab
2024-01-18 2:49 dpdklab
2024-01-18 2:49 dpdklab
2024-01-18 2:48 dpdklab
2024-01-18 2:46 dpdklab
2024-01-18 2:46 dpdklab
2024-01-18 2:45 dpdklab
2024-01-18 2:44 dpdklab
2024-01-18 2:37 dpdklab
2024-01-18 2:37 dpdklab
2024-01-18 2:36 dpdklab
2024-01-18 2:35 dpdklab
2024-01-18 2:34 dpdklab
2024-01-18 2:34 dpdklab
2024-01-18 2:28 dpdklab
2024-01-18 2:27 dpdklab
2024-01-18 2:27 dpdklab
2024-01-18 2:26 dpdklab
2024-01-18 2:23 dpdklab
2024-01-18 2:22 dpdklab
2024-01-18 2:22 dpdklab
2024-01-18 2:21 dpdklab
2024-01-18 2:19 dpdklab
2024-01-18 2:14 dpdklab
2024-01-18 2:10 dpdklab
2024-01-18 2:03 dpdklab
2024-01-18 1:50 dpdklab
2024-01-18 1:47 dpdklab
2024-01-18 1:45 dpdklab
2024-01-18 1:44 dpdklab
2024-01-18 1:43 dpdklab
2024-01-18 1:42 dpdklab
2024-01-18 1:41 dpdklab
2024-01-18 1:41 dpdklab
2024-01-18 1:41 dpdklab
2024-01-18 1:24 dpdklab
2024-01-18 1:23 dpdklab
2024-01-18 1:20 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=65a903a6.630a0220.e5c65.4e32SMTPIN_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).