From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Juraj Linkes <juraj.linkes@pantheon.tech>
Subject: |SUCCESS| pw132616-132617 [PATCH] [v5,2/2] dts: reformat to 100 line
Date: Mon, 16 Oct 2023 04:38:31 -0700 (PDT) [thread overview]
Message-ID: <652d20b7.050a0220.9ca03.b4f1SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132617
_Testing PASS_
Submitter: Juraj Linkes <juraj.linkes@pantheon.tech>
Date: Monday, October 16 2023 06:45:59
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:441e777b85f1ea1eb6a2a970ff5d5c8e027f520c
132616-132617 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Debian Bullseye | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Fedora 38 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
Debian Bullseye
Kernel: 5.4.0-122-generic
Compiler: gcc 10.2.1-6
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Fedora 38
Kernel: Depends on container host
Compiler: gcc 13.1.1
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
Debian Buster
Kernel: 5.4.0-122-generic
Compiler: gcc 8.3.0-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27934/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-10-16 11:38 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 11:38 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-18 21:13 dpdklab
2023-10-16 18:56 dpdklab
2023-10-16 13:16 dpdklab
2023-10-16 13:11 dpdklab
2023-10-16 12:25 dpdklab
2023-10-16 12:12 dpdklab
2023-10-16 12:08 dpdklab
2023-10-16 11:50 dpdklab
2023-10-16 11:46 dpdklab
2023-10-16 11:44 dpdklab
2023-10-16 11:42 dpdklab
2023-10-16 11:39 dpdklab
2023-10-16 11:38 dpdklab
2023-10-16 11:36 dpdklab
2023-10-16 11:32 dpdklab
2023-10-16 11:25 dpdklab
2023-10-16 11:20 dpdklab
2023-10-16 11:19 dpdklab
2023-10-16 11:15 dpdklab
2023-10-16 11:15 dpdklab
2023-10-16 11:15 dpdklab
2023-10-16 11:15 dpdklab
2023-10-16 11:15 dpdklab
2023-10-16 11:15 dpdklab
2023-10-16 11:14 dpdklab
2023-10-16 11:14 dpdklab
2023-10-16 11:14 dpdklab
2023-10-16 11:13 dpdklab
2023-10-16 11:11 dpdklab
2023-10-16 11:11 dpdklab
2023-10-16 11:10 dpdklab
2023-10-16 11:10 dpdklab
2023-10-16 11:09 dpdklab
2023-10-16 11:09 dpdklab
2023-10-16 11:08 dpdklab
2023-10-16 11:08 dpdklab
2023-10-16 11:08 dpdklab
2023-10-16 11:08 dpdklab
2023-10-16 11:07 dpdklab
2023-10-16 11:07 dpdklab
2023-10-16 11:06 dpdklab
2023-10-16 11:06 dpdklab
2023-10-16 11:06 dpdklab
2023-10-16 11:05 dpdklab
2023-10-16 10:59 dpdklab
2023-10-16 10:58 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=652d20b7.050a0220.9ca03.b4f1SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=juraj.linkes@pantheon.tech \
--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).