From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw138850 [PATCH] [v5] graph: expose node context as pointe
Date: Wed, 27 Mar 2024 03:29:43 -0700 (PDT) [thread overview]
Message-ID: <6603f517.050a0220.a54ac.1fd4SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240327091440.1166119-2-rjarry@redhat.com>
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/138850
_Testing PASS_
Submitter: Robin Jarry <rjarry@redhat.com>
Date: Wednesday, March 27 2024 09:14:41
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:ded4d4765171b88470e59307f10625e942f22fca
138850 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Debian Bullseye | PASS |
+---------------------+----------------+
| Debian 11 (arm) | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Fedora 39 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| Ubuntu 20.04 | PASS |
+---------------------+----------------+
| Windows Server 2022 | PASS |
+---------------------+----------------+
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
Debian 11 (arm)
Kernel: Container Host Kernel
Compiler: gcc 10.2.1
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.2.1
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
openSUSE Leap 15
Kernel: 5.4.0-167-generic
Compiler: gcc 7.5.0
Fedora 39
Kernel: Depends on container host
Compiler: clang 17.0.6
Ubuntu 22.04
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.0
Ubuntu 20.04
Kernel: 5.4.0-167-generic
Compiler: gcc 9.4.0-1ubuntu1~20.04.1
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 8.1.0 (MinGW), and MSVC VS 17.9
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29663/
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-27 10:29 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240327091440.1166119-2-rjarry@redhat.com>
2024-03-27 9:03 ` |SUCCESS| pw138850 [PATCH v5] graph: expose node context as pointers qemudev
2024-03-27 9:08 ` qemudev
2024-03-27 9:17 ` checkpatch
2024-03-27 9:57 ` |WARNING| pw138850 [PATCH] [v5] graph: expose node context as pointe dpdklab
2024-03-27 9:58 ` |SUCCESS| " dpdklab
2024-03-27 9:58 ` dpdklab
2024-03-27 9:59 ` dpdklab
2024-03-27 9:59 ` |WARNING| " dpdklab
2024-03-27 9:59 ` dpdklab
2024-03-27 9:59 ` |SUCCESS| " dpdklab
2024-03-27 9:59 ` dpdklab
2024-03-27 10:00 ` dpdklab
2024-03-27 10:00 ` dpdklab
2024-03-27 10:01 ` dpdklab
2024-03-27 10:01 ` dpdklab
2024-03-27 10:01 ` dpdklab
2024-03-27 10:01 ` dpdklab
2024-03-27 10:02 ` dpdklab
2024-03-27 10:02 ` dpdklab
2024-03-27 10:02 ` dpdklab
2024-03-27 10:03 ` dpdklab
2024-03-27 10:03 ` dpdklab
2024-03-27 10:03 ` dpdklab
2024-03-27 10:03 ` dpdklab
2024-03-27 10:03 ` dpdklab
2024-03-27 10:03 ` dpdklab
2024-03-27 10:04 ` dpdklab
2024-03-27 10:04 ` |WARNING| " dpdklab
2024-03-27 10:04 ` |SUCCESS| " dpdklab
2024-03-27 10:04 ` dpdklab
2024-03-27 10:05 ` |FAILURE| pw138850 [PATCH v5] graph: expose node context as pointers 0-day Robot
2024-03-27 10:05 ` |SUCCESS| pw138850 [PATCH] [v5] graph: expose node context as pointe dpdklab
2024-03-27 10:05 ` dpdklab
2024-03-27 10:05 ` dpdklab
2024-03-27 10:05 ` dpdklab
2024-03-27 10:06 ` dpdklab
2024-03-27 10:06 ` dpdklab
2024-03-27 10:06 ` dpdklab
2024-03-27 10:06 ` dpdklab
2024-03-27 10:06 ` dpdklab
2024-03-27 10:07 ` |WARNING| " dpdklab
2024-03-27 10:07 ` |SUCCESS| " dpdklab
2024-03-27 10:07 ` dpdklab
2024-03-27 10:08 ` dpdklab
2024-03-27 10:08 ` |WARNING| " dpdklab
2024-03-27 10:08 ` |SUCCESS| " dpdklab
2024-03-27 10:08 ` dpdklab
2024-03-27 10:09 ` dpdklab
2024-03-27 10:10 ` dpdklab
2024-03-27 10:10 ` |WARNING| " dpdklab
2024-03-27 10:10 ` dpdklab
2024-03-27 10:11 ` |SUCCESS| " dpdklab
2024-03-27 10:11 ` dpdklab
2024-03-27 10:12 ` dpdklab
2024-03-27 10:12 ` |WARNING| " dpdklab
2024-03-27 10:12 ` |SUCCESS| " dpdklab
2024-03-27 10:13 ` dpdklab
2024-03-27 10:13 ` |WARNING| " dpdklab
2024-03-27 10:13 ` |SUCCESS| " dpdklab
2024-03-27 10:14 ` dpdklab
2024-03-27 10:14 ` dpdklab
2024-03-27 10:15 ` dpdklab
2024-03-27 10:15 ` dpdklab
2024-03-27 10:16 ` |WARNING| " dpdklab
2024-03-27 10:16 ` |SUCCESS| " dpdklab
2024-03-27 10:16 ` dpdklab
2024-03-27 10:17 ` dpdklab
2024-03-27 10:18 ` dpdklab
2024-03-27 10:20 ` dpdklab
2024-03-27 10:21 ` dpdklab
2024-03-27 10:21 ` dpdklab
2024-03-27 10:22 ` dpdklab
2024-03-27 10:24 ` dpdklab
2024-03-27 10:24 ` dpdklab
2024-03-27 10:27 ` dpdklab
2024-03-27 10:28 ` dpdklab
2024-03-27 10:29 ` dpdklab [this message]
2024-03-27 10:29 ` dpdklab
2024-03-27 10:29 ` dpdklab
2024-03-27 10:31 ` dpdklab
2024-03-27 10:33 ` dpdklab
2024-03-27 10:54 ` dpdklab
2024-03-27 11:09 ` dpdklab
2024-03-27 11:34 ` dpdklab
2024-03-27 11:35 ` dpdklab
2024-03-27 12:53 ` dpdklab
2024-03-27 13:25 ` dpdklab
2024-04-02 7:32 ` dpdklab
2024-04-02 7:36 ` dpdklab
2024-04-02 7:56 ` dpdklab
2024-04-02 8:00 ` dpdklab
2024-04-02 8:04 ` 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=6603f517.050a0220.a54ac.1fd4SMTPIN_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).