From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138996 [PATCH] app/testpmd: handle IEEE1588 init fail
Date: Sat, 30 Mar 2024 02:13:18 -0700 (PDT) [thread overview]
Message-ID: <6607d7ae.170a0220.1ad31.10f9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240330074409.273916-1-huangdengdui@huawei.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138996
_Testing PASS_
Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Saturday, March 30 2024 07:44:09
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a9778aad62470a38ccbb4e09a2a6bf0cc2e0e36d
138996 --> 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/29684/
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-03-30 9:13 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240330074409.273916-1-huangdengdui@huawei.com>
2024-03-30 7:20 ` qemudev
2024-03-30 7:25 ` qemudev
2024-03-30 7:45 ` checkpatch
2024-03-30 8:35 ` dpdklab
2024-03-30 8:35 ` dpdklab
2024-03-30 8:36 ` dpdklab
2024-03-30 8:36 ` dpdklab
2024-03-30 8:36 ` dpdklab
2024-03-30 8:36 ` dpdklab
2024-03-30 8:36 ` dpdklab
2024-03-30 8:36 ` dpdklab
2024-03-30 8:37 ` dpdklab
2024-03-30 8:37 ` dpdklab
2024-03-30 8:37 ` dpdklab
2024-03-30 8:38 ` dpdklab
2024-03-30 8:38 ` dpdklab
2024-03-30 8:38 ` dpdklab
2024-03-30 8:38 ` dpdklab
2024-03-30 8:38 ` dpdklab
2024-03-30 8:39 ` dpdklab
2024-03-30 8:39 ` dpdklab
2024-03-30 8:39 ` dpdklab
2024-03-30 8:39 ` dpdklab
2024-03-30 8:40 ` dpdklab
2024-03-30 8:40 ` dpdklab
2024-03-30 8:40 ` dpdklab
2024-03-30 8:40 ` dpdklab
2024-03-30 8:41 ` dpdklab
2024-03-30 8:41 ` dpdklab
2024-03-30 8:41 ` dpdklab
2024-03-30 8:41 ` dpdklab
2024-03-30 8:42 ` dpdklab
2024-03-30 8:42 ` dpdklab
2024-03-30 8:42 ` dpdklab
2024-03-30 8:42 ` dpdklab
2024-03-30 8:43 ` dpdklab
2024-03-30 8:43 ` dpdklab
2024-03-30 8:43 ` dpdklab
2024-03-30 8:43 ` dpdklab
2024-03-30 8:44 ` dpdklab
2024-03-30 8:44 ` dpdklab
2024-03-30 8:44 ` dpdklab
2024-03-30 8:44 ` dpdklab
2024-03-30 8:44 ` dpdklab
2024-03-30 8:45 ` 0-day Robot
2024-03-30 8:45 ` dpdklab
2024-03-30 8:46 ` dpdklab
2024-03-30 8:46 ` dpdklab
2024-03-30 8:47 ` dpdklab
2024-03-30 8:47 ` dpdklab
2024-03-30 8:47 ` dpdklab
2024-03-30 8:48 ` dpdklab
2024-03-30 8:50 ` dpdklab
2024-03-30 8:50 ` dpdklab
2024-03-30 8:52 ` dpdklab
2024-03-30 8:52 ` dpdklab
2024-03-30 8:53 ` dpdklab
2024-03-30 8:54 ` dpdklab
2024-03-30 8:55 ` dpdklab
2024-03-30 8:56 ` dpdklab
2024-03-30 8:56 ` dpdklab
2024-03-30 8:56 ` dpdklab
2024-03-30 8:57 ` dpdklab
2024-03-30 8:58 ` dpdklab
2024-03-30 8:59 ` dpdklab
2024-03-30 8:59 ` dpdklab
2024-03-30 9:00 ` dpdklab
2024-03-30 9:02 ` dpdklab
2024-03-30 9:02 ` dpdklab
2024-03-30 9:05 ` dpdklab
2024-03-30 9:05 ` dpdklab
2024-03-30 9:06 ` dpdklab
2024-03-30 9:07 ` dpdklab
2024-03-30 9:08 ` dpdklab
2024-03-30 9:10 ` dpdklab
2024-03-30 9:13 ` dpdklab [this message]
2024-03-30 9:13 ` dpdklab
2024-03-30 9:14 ` dpdklab
2024-03-30 9:14 ` dpdklab
2024-03-30 9:16 ` dpdklab
2024-03-30 9:23 ` dpdklab
2024-03-30 9:26 ` dpdklab
2024-03-30 9:37 ` dpdklab
2024-03-30 9:52 ` dpdklab
2024-03-30 10:13 ` dpdklab
2024-03-30 11:16 ` dpdklab
2024-04-03 2:14 ` dpdklab
2024-04-03 2:18 ` dpdklab
2024-04-03 2:23 ` dpdklab
2024-04-03 2:27 ` dpdklab
2024-04-03 2:46 ` 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=6607d7ae.170a0220.1ad31.10f9SMTPIN_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).