From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw136433-136439 [PATCH] [v2,7/7] dts: improve test suite a
Date: Tue, 06 Feb 2024 11:21:36 -0800 (PST) [thread overview]
Message-ID: <65c286c0.050a0220.59aa8.3358SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/136439
_Testing PASS_
Submitter: Juraj Linkes <juraj.linkes@pantheon.tech>
Date: Tuesday, February 06 2024 14:57:16
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:a4ce111cc89f580b8c4aad51bdb061acbdfde86b
136433-136439 --> testing pass
Test environment and result as below:
+------------------+----------------+
| Environment | dpdk_unit_test |
+==================+================+
| CentOS Stream 9 | PASS |
+------------------+----------------+
| CentOS Stream 8 | PASS |
+------------------+----------------+
| Fedora 38 | PASS |
+------------------+----------------+
| openSUSE Leap 15 | PASS |
+------------------+----------------+
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: clang 16.0.3
openSUSE Leap 15
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 7.5.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29059/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2024-02-06 19:21 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 19:21 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-06 20:35 dpdklab
2024-02-06 20:17 dpdklab
2024-02-06 20:00 dpdklab
2024-02-06 19:50 dpdklab
2024-02-06 19:43 dpdklab
2024-02-06 19:39 dpdklab
2024-02-06 19:39 dpdklab
2024-02-06 19:32 dpdklab
2024-02-06 19:31 dpdklab
2024-02-06 19:29 dpdklab
2024-02-06 19:29 dpdklab
2024-02-06 19:29 dpdklab
2024-02-06 19:28 dpdklab
2024-02-06 19:28 dpdklab
2024-02-06 19:28 dpdklab
2024-02-06 19:28 dpdklab
2024-02-06 19:27 dpdklab
2024-02-06 19:27 dpdklab
2024-02-06 19:27 dpdklab
2024-02-06 19:27 dpdklab
2024-02-06 19:27 dpdklab
2024-02-06 19:26 dpdklab
2024-02-06 19:26 dpdklab
2024-02-06 19:26 dpdklab
2024-02-06 19:25 dpdklab
2024-02-06 19:25 dpdklab
2024-02-06 19:24 dpdklab
2024-02-06 19:24 dpdklab
2024-02-06 19:24 dpdklab
2024-02-06 19:24 dpdklab
2024-02-06 19:23 dpdklab
2024-02-06 19:23 dpdklab
2024-02-06 19:23 dpdklab
2024-02-06 19:23 dpdklab
2024-02-06 19:23 dpdklab
2024-02-06 19:23 dpdklab
2024-02-06 19:22 dpdklab
2024-02-06 19:22 dpdklab
2024-02-06 19:22 dpdklab
2024-02-06 19:22 dpdklab
2024-02-06 19:22 dpdklab
2024-02-06 19:21 dpdklab
2024-02-06 19:21 dpdklab
2024-02-06 19:21 dpdklab
2024-02-06 19:20 dpdklab
2024-02-06 19:20 dpdklab
2024-02-06 19:20 dpdklab
2024-02-06 19:20 dpdklab
2024-02-06 19:20 dpdklab
2024-02-06 19:20 dpdklab
2024-02-06 19:20 dpdklab
2024-02-06 19:19 dpdklab
2024-02-06 19:19 dpdklab
2024-02-06 19:19 dpdklab
2024-02-06 19:19 dpdklab
2024-02-06 19:19 dpdklab
2024-02-06 19:18 dpdklab
2024-02-06 19:18 dpdklab
2024-02-06 19:17 dpdklab
2024-02-06 19:16 dpdklab
2024-02-06 19:16 dpdklab
2024-02-06 19:15 dpdklab
2024-02-06 19:04 dpdklab
2024-02-06 19:03 dpdklab
2024-02-06 19:03 dpdklab
2024-02-06 19:02 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=65c286c0.050a0220.59aa8.3358SMTPIN_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).