From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw146309-146312 [PATCH] [v3,4/4] net/ice: limit the number
Date: Tue, 22 Oct 2024 05:58:00 -0700 (PDT) [thread overview]
Message-ID: <6717a158.050a0220.23e28c.0de4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20241018143822.2784548-5-bruce.richardson@intel.com>
Test-Label: iol-unit-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/146312
_Testing pending RETEST #1_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Friday, October 18 2024 14:38:22
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:cff6dba7ff8521df410b40399fd8aca5b450a05b
146309-146312 --> testing pending
Upstream job id: Generic-Unit-Test-DPDK#280124
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2022 | PEND |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian 12 | PEND |
+---------------------+----------------+
| Fedora 37 | PEND |
+---------------------+----------------+
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.4.1 20231218 (Red Hat 11.4.1-3)
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1 20230508 (Red Hat 12.3.1-1)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/31554/
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-10-22 12:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241018143822.2784548-5-bruce.richardson@intel.com>
2024-10-18 14:40 ` |SUCCESS| pw146312 [PATCH v3 4/4] net/ice: limit the number of queues to sched capabilities checkpatch
2024-10-18 17:23 ` 0-day Robot
2024-10-19 20:36 ` |PENDING| pw146309-146312 [PATCH] [v3,4/4] net/ice: limit the number dpdklab
2024-10-19 20:41 ` |SUCCESS| " dpdklab
2024-10-19 20:51 ` |PENDING| " dpdklab
2024-10-19 21:22 ` dpdklab
2024-10-19 21:27 ` |FAILURE| " dpdklab
2024-10-19 21:58 ` |SUCCESS| " dpdklab
2024-10-19 23:01 ` |FAILURE| " dpdklab
2024-10-19 23:34 ` dpdklab
2024-10-20 1:35 ` |SUCCESS| " dpdklab
2024-10-20 6:59 ` |PENDING| " dpdklab
2024-10-20 7:40 ` |FAILURE| " dpdklab
2024-10-20 8:09 ` |SUCCESS| " dpdklab
2024-10-20 10:54 ` dpdklab
2024-10-20 14:23 ` dpdklab
2024-10-21 4:07 ` |SUCCESS| pw146309-146312 [PATCH v3 4/4] net/ice: limit the number of queues to sched capabilities qemudev
2024-10-21 4:11 ` qemudev
2024-10-22 1:52 ` |SUCCESS| pw146309-146312 [PATCH] [v3,4/4] net/ice: limit the number dpdklab
2024-10-22 3:20 ` |SUCCESS| pw146309-146312 [PATCH v3 4/4] net/ice: limit the number of queues to sched capabilities qemudev
2024-10-22 3:20 ` qemudev
2024-10-22 4:58 ` |SUCCESS| pw146309-146312 [PATCH] [v3,4/4] net/ice: limit the number dpdklab
2024-10-22 5:08 ` dpdklab
2024-10-22 5:31 ` dpdklab
2024-10-22 6:08 ` dpdklab
2024-10-22 8:36 ` dpdklab
2024-10-22 12:58 ` dpdklab [this message]
2024-10-22 13:06 ` |PENDING| " dpdklab
2024-10-22 13:21 ` dpdklab
2024-10-22 13:29 ` |SUCCESS| " dpdklab
2024-10-22 13:29 ` dpdklab
2024-10-22 13:32 ` dpdklab
2024-10-22 14:19 ` dpdklab
2024-10-22 15:10 ` dpdklab
2024-10-22 21:48 ` dpdklab
2024-10-23 1:04 ` dpdklab
2024-10-23 2:32 ` |PENDING| " dpdklab
2024-10-23 2:53 ` |SUCCESS| " dpdklab
2024-10-23 10:44 ` dpdklab
2024-10-23 14:00 ` |WARNING| " 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=6717a158.050a0220.23e28c.0de4SMTPIN_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).