From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137504-137507 [PATCH] [v6,4/4] test: add unit test for p
Date: Thu, 29 Feb 2024 15:50:23 -0800 (PST) [thread overview]
Message-ID: <65e1183f.170a0220.3fe53.433dSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240229160308.365277-5-paul.szczepanek@arm.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/137507
_Testing PASS_
Submitter: Paul Szczepanek <paul.szczepanek@arm.com>
Date: Thursday, February 29 2024 16:03:08
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137504-137507 --> testing pass
Test environment and result as below:
+---------------------+--------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_mingw64_compile |
+=====================+====================+======================+
| FreeBSD 13.2 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian Bullseye | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 37 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 20.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| CentOS Stream 9 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| RHEL8 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Ubuntu 22.04 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| openSUSE Leap 15 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Debian 12 (arm) | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Fedora 38 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Alpine | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2022 | PASS | SKIPPED |
+---------------------+--------------------+----------------------+
| Windows Server 2019 | PASS | PASS |
+---------------------+--------------------+----------------------+
FreeBSD 13.2
Kernel: 13.2
Compiler: clang 11.3.0
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
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
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.0
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
Debian 12 (arm)
Kernel: Container Host Kernel
Compiler: gcc 11
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
Alpine
Kernel: 5.4.0-73-generic
Compiler: gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424
Windows Server 2022
Kernel: OS Build 20348.2031
Compiler: MSVC VS-Preview
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/29342/
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-02-29 23:50 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229160308.365277-5-paul.szczepanek@arm.com>
2024-02-29 16:06 ` |SUCCESS| pw137507 [PATCH v6 4/4] test: add unit test for ptr compression checkpatch
2024-02-29 17:05 ` 0-day Robot
2024-02-29 19:03 ` |SUCCESS| pw137504-137507 [PATCH] [v6,4/4] test: add unit test for p dpdklab
2024-02-29 19:06 ` dpdklab
2024-02-29 19:09 ` dpdklab
2024-02-29 19:17 ` dpdklab
2024-02-29 19:20 ` dpdklab
2024-02-29 19:20 ` dpdklab
2024-02-29 19:21 ` dpdklab
2024-02-29 19:23 ` dpdklab
2024-02-29 19:28 ` dpdklab
2024-02-29 19:30 ` dpdklab
2024-02-29 19:35 ` dpdklab
2024-02-29 19:37 ` dpdklab
2024-02-29 19:48 ` dpdklab
2024-02-29 19:50 ` dpdklab
2024-02-29 19:51 ` dpdklab
2024-02-29 19:53 ` dpdklab
2024-02-29 19:58 ` dpdklab
2024-02-29 20:04 ` dpdklab
2024-02-29 21:51 ` dpdklab
2024-02-29 22:00 ` dpdklab
2024-02-29 22:00 ` dpdklab
2024-02-29 22:13 ` dpdklab
2024-02-29 22:13 ` dpdklab
2024-02-29 22:13 ` dpdklab
2024-02-29 22:13 ` dpdklab
2024-02-29 22:13 ` dpdklab
2024-02-29 22:14 ` dpdklab
2024-02-29 22:15 ` dpdklab
2024-02-29 22:16 ` dpdklab
2024-02-29 22:16 ` dpdklab
2024-02-29 22:16 ` dpdklab
2024-02-29 22:16 ` dpdklab
2024-02-29 22:17 ` dpdklab
2024-02-29 22:18 ` dpdklab
2024-02-29 22:19 ` dpdklab
2024-02-29 22:20 ` dpdklab
2024-02-29 22:21 ` dpdklab
2024-02-29 22:21 ` dpdklab
2024-02-29 22:21 ` dpdklab
2024-02-29 22:26 ` dpdklab
2024-02-29 22:27 ` dpdklab
2024-02-29 22:27 ` dpdklab
2024-02-29 22:27 ` dpdklab
2024-02-29 22:27 ` dpdklab
2024-02-29 22:28 ` dpdklab
2024-02-29 22:28 ` dpdklab
2024-02-29 22:29 ` dpdklab
2024-02-29 22:29 ` dpdklab
2024-02-29 22:29 ` dpdklab
2024-02-29 22:30 ` dpdklab
2024-02-29 22:30 ` dpdklab
2024-02-29 22:30 ` dpdklab
2024-02-29 22:30 ` dpdklab
2024-02-29 22:31 ` dpdklab
2024-02-29 22:34 ` dpdklab
2024-02-29 22:36 ` dpdklab
2024-02-29 22:37 ` dpdklab
2024-02-29 22:40 ` dpdklab
2024-02-29 22:40 ` dpdklab
2024-02-29 22:49 ` dpdklab
2024-02-29 22:50 ` dpdklab
2024-02-29 23:13 ` dpdklab
2024-02-29 23:37 ` dpdklab
2024-02-29 23:50 ` dpdklab [this message]
2024-03-01 5:58 ` dpdklab
2024-03-01 9:35 ` dpdklab
2024-03-01 9:40 ` dpdklab
2024-03-01 9:47 ` dpdklab
2024-03-01 9:52 ` dpdklab
2024-03-02 9:57 ` dpdklab
2024-03-03 14:30 ` dpdklab
2024-03-03 15:02 ` dpdklab
2024-03-03 15:35 ` 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=65e1183f.170a0220.3fe53.433dSMTPIN_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).