From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Subject: |SUCCESS| pw131817-131818 [PATCH] [v4,3/3] doc: add dispatcher progr
Date: Fri, 22 Sep 2023 04:54:29 -0700 (PDT) [thread overview]
Message-ID: <650d8075.9f0a0220.4e83e.9154SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/131818
_Testing PASS_
Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Friday, September 22 2023 07:38:25
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:aaee22f1f61fb1df019a058580369b92d2cfa5c1
131817-131818 --> testing pass
Test environment and result as below:
+---------------------+--------------------+
| Environment | dpdk_meson_compile |
+=====================+====================+
| FreeBSD 13 | PASS |
+---------------------+--------------------+
| Windows Server 2019 | PASS |
+---------------------+--------------------+
| CentOS Stream 8 | PASS |
+---------------------+--------------------+
| CentOS Stream 9 | PASS |
+---------------------+--------------------+
| openSUSE Leap 15 | PASS |
+---------------------+--------------------+
| Debian Buster | PASS |
+---------------------+--------------------+
FreeBSD 13
Kernel: 13.0
Compiler: clang 11.0.1
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
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27695/
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-22 11:54 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 11:54 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-22 13:36 dpdklab
2023-09-22 13:12 dpdklab
2023-09-22 13:11 dpdklab
2023-09-22 13:10 dpdklab
2023-09-22 13:06 dpdklab
2023-09-22 13:05 dpdklab
2023-09-22 13:01 dpdklab
2023-09-22 12:50 dpdklab
2023-09-22 12:50 dpdklab
2023-09-22 12:46 dpdklab
2023-09-22 12:46 dpdklab
2023-09-22 12:41 dpdklab
2023-09-22 12:37 dpdklab
2023-09-22 12:33 dpdklab
2023-09-22 12:29 dpdklab
2023-09-22 12:22 dpdklab
2023-09-22 12:17 dpdklab
2023-09-22 12:15 dpdklab
2023-09-22 12:14 dpdklab
2023-09-22 12:13 dpdklab
2023-09-22 12:13 dpdklab
2023-09-22 12:11 dpdklab
2023-09-22 12:11 dpdklab
2023-09-22 12:09 dpdklab
2023-09-22 12:09 dpdklab
2023-09-22 12:08 dpdklab
2023-09-22 12:07 dpdklab
2023-09-22 12:07 dpdklab
2023-09-22 12:06 dpdklab
2023-09-22 12:06 dpdklab
2023-09-22 12:06 dpdklab
2023-09-22 12:05 dpdklab
2023-09-22 12:05 dpdklab
2023-09-22 12:04 dpdklab
2023-09-22 12:04 dpdklab
2023-09-22 12:04 dpdklab
2023-09-22 12:03 dpdklab
2023-09-22 12:03 dpdklab
2023-09-22 12:03 dpdklab
2023-09-22 12:02 dpdklab
2023-09-22 12:02 dpdklab
2023-09-22 12:02 dpdklab
2023-09-22 12:01 dpdklab
2023-09-22 12:00 dpdklab
2023-09-22 11:57 dpdklab
2023-09-22 11:38 dpdklab
2023-09-22 11:30 dpdklab
2023-09-22 11: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=650d8075.9f0a0220.4e83e.9154SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=mattias.ronnblom@ericsson.com \
--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).