From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw135901 [PATCH] [v4] dts: add Dockerfile
Date: Thu, 18 Jan 2024 03:02:59 -0800 (PST) [thread overview]
Message-ID: <65a90563.810a0220.73a61.2848SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/135901
_Testing PASS_
Submitter: Jeremy Spewock <jspewock@iol.unh.edu>
Date: Tuesday, January 16 2024 19:18:14
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:d4af9a82063e4c39568191eaa12955d3ca39581a
135901 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
| Fedora 37 | PASS |
+---------------------+----------------+
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
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
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
Fedora 37
Kernel: Depends on container host system
Compiler: gcc 12.3.1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/28879/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-01-18 11:03 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 11:02 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-01-23 21:45 dpdklab
2024-01-18 15:08 dpdklab
2024-01-18 14:25 dpdklab
2024-01-18 13:05 dpdklab
2024-01-18 12:11 dpdklab
2024-01-18 11:45 dpdklab
2024-01-18 11:45 dpdklab
2024-01-18 11:39 dpdklab
2024-01-18 11:38 dpdklab
2024-01-18 11:37 dpdklab
2024-01-18 11:36 dpdklab
2024-01-18 11:27 dpdklab
2024-01-18 11:15 dpdklab
2024-01-18 11:14 dpdklab
2024-01-18 11:14 dpdklab
2024-01-18 11:14 dpdklab
2024-01-18 11:13 dpdklab
2024-01-18 11:13 dpdklab
2024-01-18 11:13 dpdklab
2024-01-18 11:13 dpdklab
2024-01-18 11:04 dpdklab
2024-01-18 10:59 dpdklab
2024-01-18 10:58 dpdklab
2024-01-18 10:58 dpdklab
2024-01-18 10:56 dpdklab
2024-01-18 10:55 dpdklab
2024-01-18 10:50 dpdklab
2024-01-18 10:50 dpdklab
2024-01-18 10:37 dpdklab
2024-01-18 10:27 dpdklab
2024-01-18 10:23 dpdklab
2024-01-18 10:23 dpdklab
2024-01-18 10:21 dpdklab
2024-01-18 9:49 dpdklab
2024-01-18 9:44 dpdklab
2024-01-18 9:10 dpdklab
2024-01-18 8:52 dpdklab
2024-01-18 8:52 dpdklab
2024-01-18 8:51 dpdklab
2024-01-18 8:51 dpdklab
2024-01-18 8:51 dpdklab
2024-01-18 8:50 dpdklab
2024-01-18 8:50 dpdklab
2024-01-18 8:50 dpdklab
2024-01-18 8:46 dpdklab
2024-01-18 8:38 dpdklab
2024-01-18 8:21 dpdklab
2024-01-18 8:20 dpdklab
2024-01-18 8:18 dpdklab
2024-01-18 8:18 dpdklab
2024-01-18 8:17 dpdklab
2024-01-18 8:15 dpdklab
2024-01-18 8:13 dpdklab
2024-01-18 8:11 dpdklab
2024-01-18 8:09 dpdklab
2024-01-18 8:06 dpdklab
2024-01-18 8:05 dpdklab
2024-01-18 7:54 dpdklab
2024-01-18 7:48 dpdklab
2024-01-18 7:47 dpdklab
2024-01-18 7:45 dpdklab
2024-01-18 7:43 dpdklab
2024-01-18 7:40 dpdklab
2024-01-18 7:06 dpdklab
2024-01-18 6:51 dpdklab
[not found] <20240116191814.31316-1-jspewock@iol.unh.edu>
2024-01-16 20:03 ` |SUCCESS| pw135901 [PATCH v4] " 0-day Robot
2024-01-17 2:08 ` qemudev
2024-01-17 2:13 ` qemudev
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=65a90563.810a0220.73a61.2848SMTPIN_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).