From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137510 [PATCH] doc: update link to DevX integration on W
Date: Thu, 29 Feb 2024 18:16:16 -0800 (PST) [thread overview]
Message-ID: <65e13a70.050a0220.e45f2.90f2SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240229164526.1144333-1-alialnu@nvidia.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137510
_Testing PASS_
Submitter: Ali Alnubani <alialnu@nvidia.com>
Date: Thursday, February 29 2024 16:45:26
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:387aefe9fab8f1033071659a758ccda61a220ffd
137510 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian 12 (arm) | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Alpine | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Ubuntu 20.04
Kernel: 5.4.0-153-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Ubuntu 22.04
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
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)
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29344/
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-03-01 2:16 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229164526.1144333-1-alialnu@nvidia.com>
2024-02-29 16:24 ` |SUCCESS| pw137510 [PATCH] doc: update link to DevX integration on Windows qemudev
2024-02-29 16:29 ` qemudev
2024-02-29 16:48 ` checkpatch
2024-02-29 17:45 ` 0-day Robot
2024-02-29 20:47 ` |SUCCESS| pw137510 [PATCH] doc: update link to DevX integration on W dpdklab
2024-02-29 20:49 ` dpdklab
2024-02-29 20:55 ` dpdklab
2024-02-29 20:56 ` dpdklab
2024-02-29 21:00 ` dpdklab
2024-02-29 21:04 ` dpdklab
2024-02-29 21:08 ` dpdklab
2024-02-29 21:11 ` dpdklab
2024-02-29 21:13 ` dpdklab
2024-02-29 21:14 ` dpdklab
2024-02-29 21:14 ` dpdklab
2024-02-29 21:15 ` dpdklab
2024-02-29 21:16 ` dpdklab
2024-02-29 21:18 ` dpdklab
2024-02-29 21:26 ` dpdklab
2024-02-29 21:33 ` dpdklab
2024-02-29 21:35 ` dpdklab
2024-02-29 21:42 ` dpdklab
2024-03-01 1:03 ` dpdklab
2024-03-01 1:06 ` dpdklab
2024-03-01 1:07 ` dpdklab
2024-03-01 1:07 ` dpdklab
2024-03-01 1:08 ` dpdklab
2024-03-01 1:21 ` dpdklab
2024-03-01 1:31 ` dpdklab
2024-03-01 1:31 ` dpdklab
2024-03-01 1:33 ` dpdklab
2024-03-01 1:34 ` dpdklab
2024-03-01 1:42 ` dpdklab
2024-03-01 1:43 ` dpdklab
2024-03-01 1:44 ` dpdklab
2024-03-01 1:44 ` dpdklab
2024-03-01 1:49 ` dpdklab
2024-03-01 1:52 ` dpdklab
2024-03-01 1:52 ` dpdklab
2024-03-01 1:53 ` dpdklab
2024-03-01 1:54 ` dpdklab
2024-03-01 1:55 ` dpdklab
2024-03-01 1:56 ` dpdklab
2024-03-01 1:57 ` dpdklab
2024-03-01 1:59 ` dpdklab
2024-03-01 2:04 ` dpdklab
2024-03-01 2:04 ` dpdklab
2024-03-01 2:05 ` dpdklab
2024-03-01 2:06 ` dpdklab
2024-03-01 2:08 ` dpdklab
2024-03-01 2:09 ` dpdklab
2024-03-01 2:09 ` dpdklab
2024-03-01 2:10 ` dpdklab
2024-03-01 2:11 ` dpdklab
2024-03-01 2:11 ` dpdklab
2024-03-01 2:12 ` dpdklab
2024-03-01 2:12 ` dpdklab
2024-03-01 2:12 ` dpdklab
2024-03-01 2:13 ` dpdklab
2024-03-01 2:13 ` dpdklab
2024-03-01 2:14 ` dpdklab
2024-03-01 2:14 ` dpdklab
2024-03-01 2:16 ` dpdklab [this message]
2024-03-01 2:21 ` dpdklab
2024-03-01 2:27 ` dpdklab
2024-03-01 2:35 ` dpdklab
2024-03-01 2:45 ` dpdklab
2024-03-01 4:44 ` dpdklab
2024-03-01 7:54 ` dpdklab
2024-03-01 11:20 ` dpdklab
2024-03-01 11:24 ` dpdklab
2024-03-01 11:29 ` dpdklab
2024-03-01 11:34 ` dpdklab
2024-03-02 12:02 ` dpdklab
2024-03-03 22:38 ` dpdklab
2024-03-03 23:11 ` dpdklab
2024-03-03 23:43 ` 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=65e13a70.050a0220.e45f2.90f2SMTPIN_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).