From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136798 [PATCH] [V2] pipeline: remove limitation on numbe
Date: Thu, 15 Feb 2024 00:29:50 -0800 (PST) [thread overview]
Message-ID: <65cdcb7e.050a0220.ca48f.29e1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136798
_Testing PASS_
Submitter: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Date: Wednesday, February 14 2024 20:58:36
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:8d85afb19af706de662e7ee686e6e437f835c6e3
136798 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29154/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-15 8:29 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 8:29 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-15 11:25 dpdklab
2024-02-15 11:16 dpdklab
2024-02-15 10:58 dpdklab
2024-02-15 10:44 dpdklab
2024-02-15 10:43 dpdklab
2024-02-15 9:58 dpdklab
2024-02-15 9:57 dpdklab
2024-02-15 9:48 dpdklab
2024-02-15 9:42 dpdklab
2024-02-15 9:35 dpdklab
2024-02-15 9:24 dpdklab
2024-02-15 9:08 dpdklab
2024-02-15 8:56 dpdklab
2024-02-15 8:55 dpdklab
2024-02-15 8:45 dpdklab
2024-02-15 8:44 dpdklab
2024-02-15 8:42 dpdklab
2024-02-15 8:40 dpdklab
2024-02-15 8:38 dpdklab
2024-02-15 8:36 dpdklab
2024-02-15 8:34 dpdklab
2024-02-15 8:33 dpdklab
2024-02-15 8:31 dpdklab
2024-02-15 8:31 dpdklab
2024-02-15 8:31 dpdklab
2024-02-15 8:30 dpdklab
2024-02-15 8:30 dpdklab
2024-02-15 8:29 dpdklab
2024-02-15 8:28 dpdklab
2024-02-15 8:24 dpdklab
2024-02-15 8:21 dpdklab
2024-02-15 8:20 dpdklab
2024-02-15 8:20 dpdklab
2024-02-15 8:20 dpdklab
2024-02-15 8:19 dpdklab
2024-02-15 8:19 dpdklab
2024-02-15 8:19 dpdklab
2024-02-15 8:18 dpdklab
2024-02-15 8:18 dpdklab
2024-02-15 8:18 dpdklab
2024-02-15 8:18 dpdklab
2024-02-15 8:18 dpdklab
2024-02-15 8:17 dpdklab
2024-02-15 8:17 dpdklab
2024-02-15 8:17 dpdklab
2024-02-15 8:16 dpdklab
2024-02-15 8:16 dpdklab
2024-02-15 8:16 dpdklab
2024-02-15 8:14 dpdklab
2024-02-15 8:14 dpdklab
2024-02-15 8:13 dpdklab
2024-02-15 8:13 dpdklab
2024-02-15 8:13 dpdklab
2024-02-15 8:11 dpdklab
2024-02-15 8:03 dpdklab
2024-02-15 7:58 dpdklab
2024-02-15 7:56 dpdklab
2024-02-15 7:47 dpdklab
2024-02-15 7:47 dpdklab
2024-02-15 7:45 dpdklab
2024-02-15 7:42 dpdklab
2024-02-15 7:35 dpdklab
2024-02-15 7:34 dpdklab
2024-02-15 7:24 dpdklab
2024-02-15 7:23 dpdklab
2024-02-15 7:21 dpdklab
2024-02-15 7:21 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=65cdcb7e.050a0220.ca48f.29e1SMTPIN_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).