From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw131865-131869 [PATCH] [v4,5/5] doc: add generic flow doc
Date: Sun, 24 Sep 2023 20:26:52 -0700 (PDT) [thread overview]
Message-ID: <6510fdfc.a70a0220.6f209.95a0SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131869
_Testing PASS_
Submitter: Qi Zhang <qi.z.zhang@intel.com>
Date: Monday, September 25 2023 10:33:24
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2744cb6ef086435ae7d3d997b9b62a3c74cec224
131865-131869 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
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
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27707/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-09-25 3:27 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 3:26 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-25 4:29 dpdklab
2023-09-25 4:09 dpdklab
2023-09-25 3:36 dpdklab
2023-09-25 3:36 dpdklab
2023-09-25 3:35 dpdklab
2023-09-25 3:35 dpdklab
2023-09-25 3:34 dpdklab
2023-09-25 3:33 dpdklab
2023-09-25 3:33 dpdklab
2023-09-25 3:31 dpdklab
2023-09-25 3:29 dpdklab
2023-09-25 3:27 dpdklab
2023-09-25 3:27 dpdklab
2023-09-25 3:26 dpdklab
2023-09-25 3:26 dpdklab
2023-09-25 3:26 dpdklab
2023-09-25 3:05 dpdklab
2023-09-25 3:04 dpdklab
2023-09-25 3:04 dpdklab
2023-09-25 3:04 dpdklab
2023-09-25 3:03 dpdklab
2023-09-25 3:03 dpdklab
2023-09-25 3:03 dpdklab
2023-09-25 3:03 dpdklab
2023-09-25 3:03 dpdklab
2023-09-25 3:02 dpdklab
2023-09-25 3:01 dpdklab
2023-09-25 3:01 dpdklab
2023-09-25 3:01 dpdklab
2023-09-25 2:58 dpdklab
2023-09-25 2:58 dpdklab
2023-09-25 2:57 dpdklab
2023-09-25 2:56 dpdklab
2023-09-25 2:56 dpdklab
2023-09-25 2:56 dpdklab
2023-09-25 2:55 dpdklab
2023-09-25 2:55 dpdklab
2023-09-25 2:55 dpdklab
2023-09-25 2:55 dpdklab
2023-09-25 2:55 dpdklab
2023-09-25 2:55 dpdklab
2023-09-25 2:55 dpdklab
2023-09-25 2:53 dpdklab
2023-09-25 2:53 dpdklab
2023-09-25 2:51 dpdklab
2023-09-25 2:50 dpdklab
2023-09-25 2:49 dpdklab
2023-09-25 2:48 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=6510fdfc.a70a0220.6f209.95a0SMTPIN_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).