From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdklab@iol.unh.edu, David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: |SUCCESS| pw123211 [PATCH] doc: rebuild all Sphinx guides
Date: Wed, 8 Feb 2023 03:18:44 +0000 (UTC) [thread overview]
Message-ID: <20230208031844.CC572600AE@dpdk-ubuntu.dpdklab.iol.unh.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 2210 bytes --]
Test-Label: iol-testing
Test-Status: SUCCESS
http://dpdk.org/patch/123211
_Testing PASS_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Tuesday, February 07 2023 08:43:52
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:56ee8af9fd80493a9dd888ccc01ef4f1db02e491
123211 --> testing pass
Test environment and result as below:
+-------------------------------+----------------+
| Environment | dpdk_unit_test |
+===============================+================+
| Ubuntu 20.04 ARM GCC Native | PASS |
+-------------------------------+----------------+
| Ubuntu 20.04 ARM Clang Native | PASS |
+-------------------------------+----------------+
| Windows Server 2019 | PASS |
+-------------------------------+----------------+
| Ubuntu 20.04 | PASS |
+-------------------------------+----------------+
| RHEL 7 | PASS |
+-------------------------------+----------------+
| openSUSE Leap 15 | PASS |
+-------------------------------+----------------+
| RHEL8 | PASS |
+-------------------------------+----------------+
| Ubuntu 22.04 | PASS |
+-------------------------------+----------------+
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Ubuntu 20.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 9.3.0-17ubuntu1~20.04
RHEL 7
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 4.8.5 20150623 (Red Hat 4.8.5-44)
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
RHEL8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.3.1 20191121 (Red Hat 8.3.1-5)
Ubuntu 22.04
Kernel: Container Host Kernel
Compiler: gcc 12.2.1-2
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/25247/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-02-08 3:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 3:18 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-08 23:35 dpdklab
2023-02-08 16:07 dpdklab
2023-02-08 11:34 dpdklab
2023-02-08 3:37 dpdklab
2023-02-08 3:37 dpdklab
2023-02-08 3:35 dpdklab
2023-02-08 3:33 dpdklab
2023-02-08 3:24 dpdklab
2023-02-08 3:18 dpdklab
2023-02-08 3:18 dpdklab
2023-02-08 3:13 dpdklab
2023-02-08 1:29 dpdklab
2023-02-07 14:59 dpdklab
2023-02-07 10:30 dpdklab
2023-02-07 10:10 dpdklab
2023-02-07 10:05 dpdklab
2023-02-07 9:51 dpdklab
2023-02-07 9:49 dpdklab
2023-02-07 9:46 dpdklab
2023-02-07 9:39 dpdklab
2023-02-07 9:38 dpdklab
2023-02-07 9:35 dpdklab
2023-02-07 9:33 dpdklab
2023-02-07 9:31 dpdklab
[not found] <20230207084352.3325416-1-thomas@monjalon.net>
2023-02-07 8:45 ` checkpatch
2023-02-07 8:51 ` qemudev
2023-02-07 8:55 ` qemudev
2023-02-07 9:59 ` 0-day Robot
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=20230208031844.CC572600AE@dpdk-ubuntu.dpdklab.iol.unh.edu \
--to=dpdklab@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=test-report@dpdk.org \
--cc=thomas@monjalon.net \
/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).