From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw143378 [PATCH] [v1] net/ice: fix incorrect reading of PH
Date: Mon, 26 Aug 2024 18:39:13 -0700 (PDT) [thread overview]
Message-ID: <66cd2e41.170a0220.222270.869aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240823110133.456934-1-soumyadeep.hore@intel.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/143378
_Testing PASS RETEST #1_
Submitter: Soumyadeep Hore <soumyadeep.hore@intel.com>
Date: Friday, August 23 2024 11:01:33
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:22637bd9a8c26f20bf12b69f90f085d50eda9d66
143378 --> testing pass
Upstream job id: Template-DTS-Pipeline#177134
Test environment and result as below:
+--------------------+----------------------+----------------------+
| Environment | compressdev_zlib_pmd | dpdk_fips_validation |
+====================+======================+======================+
| Ubuntu 22.04 (ARM) | PASS | SKIPPED |
+--------------------+----------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+--------------------+----------------------+----------------------+
| Ubuntu 20.04 | SKIPPED | PASS |
+--------------------+----------------------+----------------------+
Ubuntu 22.04 (ARM)
Kernel: 5.15.0-97-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 22.04
Kernel: 5.15.0-100-generic
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Ubuntu 20.04
Kernel: Depends on container host
Compiler: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30846/
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-08-27 1:39 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240823110133.456934-1-soumyadeep.hore@intel.com>
2024-08-23 11:35 ` |SUCCESS| pw143378 [PATCH v1] net/ice: fix incorrect reading of PHY timestamp qemudev
2024-08-23 11:40 ` qemudev
2024-08-23 11:56 ` checkpatch
2024-08-23 12:43 ` 0-day Robot
2024-08-23 16:24 ` |SUCCESS| pw143378 [PATCH] [v1] net/ice: fix incorrect reading of PH dpdklab
2024-08-23 16:36 ` dpdklab
2024-08-23 16:55 ` dpdklab
2024-08-23 16:59 ` dpdklab
2024-08-23 17:02 ` dpdklab
2024-08-23 17:38 ` |FAILURE| " dpdklab
2024-08-23 19:15 ` |SUCCESS| " dpdklab
2024-08-23 19:17 ` dpdklab
2024-08-23 19:42 ` dpdklab
2024-08-23 19:51 ` dpdklab
2024-08-23 22:40 ` dpdklab
2024-08-23 22:46 ` dpdklab
2024-08-23 22:52 ` dpdklab
2024-08-23 23:00 ` dpdklab
2024-08-23 23:08 ` dpdklab
2024-08-23 23:17 ` dpdklab
2024-08-23 23:32 ` dpdklab
2024-08-23 23:34 ` dpdklab
2024-08-24 0:03 ` dpdklab
2024-08-24 0:06 ` dpdklab
2024-08-24 4:28 ` dpdklab
2024-08-24 4:29 ` |PENDING| " dpdklab
2024-08-24 4:37 ` dpdklab
2024-08-24 4:38 ` |FAILURE| " dpdklab
2024-08-24 4:42 ` dpdklab
2024-08-24 5:06 ` |WARNING| " dpdklab
2024-08-24 5:42 ` |SUCCESS| " dpdklab
2024-08-24 5:44 ` dpdklab
2024-08-24 6:18 ` |PENDING| " dpdklab
2024-08-24 7:11 ` |SUCCESS| " dpdklab
2024-08-24 7:22 ` dpdklab
2024-08-24 7:35 ` dpdklab
2024-08-24 7:57 ` dpdklab
2024-08-24 8:14 ` dpdklab
2024-08-24 8:25 ` dpdklab
2024-08-24 8:29 ` dpdklab
2024-08-24 8:32 ` dpdklab
2024-08-24 8:40 ` dpdklab
2024-08-24 12:17 ` dpdklab
2024-08-24 12:59 ` dpdklab
2024-08-26 14:33 ` dpdklab
2024-08-26 14:34 ` |WARNING| " dpdklab
2024-08-26 15:51 ` |SUCCESS| " dpdklab
2024-08-26 19:06 ` |WARNING| " dpdklab
2024-08-27 1:39 ` dpdklab [this message]
2024-08-27 1:50 ` |SUCCESS| " dpdklab
2024-08-27 1:54 ` dpdklab
2024-08-27 1:58 ` dpdklab
2024-08-27 2:02 ` dpdklab
2024-08-27 2:21 ` dpdklab
2024-08-27 2:59 ` dpdklab
2024-08-27 10:24 ` dpdklab
2024-08-27 14:23 ` dpdklab
2024-09-20 5:35 ` dpdklab
2024-09-20 17:01 ` dpdklab
2024-09-21 22:26 ` dpdklab
2024-09-21 22:37 ` 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=66cd2e41.170a0220.222270.869aSMTPIN_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).