From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>
Subject: |SUCCESS| pw130786 [PATCH] [v1,1/1] eal/random: fix random state ini
Date: Mon, 28 Aug 2023 12:53:38 -0700 (PDT) [thread overview]
Message-ID: <64ecfb42.810a0220.2b29f.2fbfSMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-unit-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/130786
_Testing PASS_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Monday, August 28 2023 12:06:40
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:b2f967dcae6940b4707437d024747318a159f9b3
130786 --> testing pass
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| CentOS Stream 8 | PASS |
+---------------------+----------------+
| CentOS Stream 9 | PASS |
+---------------------+----------------+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| Ubuntu 22.04 | PASS |
+---------------------+----------------+
| openSUSE Leap 15 | PASS |
+---------------------+----------------+
| Debian Buster | PASS |
+---------------------+----------------+
CentOS Stream 8
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 8.4.1 20200928
CentOS Stream 9
Kernel: 4.18.0-240.10.1.el8_3.x86_64
Compiler: gcc 11.3.1 20220421
Windows Server 2019
Kernel: 10.0
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
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 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/27457/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-08-28 19:53 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 19:53 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-29 9:28 dpdklab
2023-08-29 9:23 dpdklab
2023-08-29 9:20 dpdklab
2023-08-29 9:02 dpdklab
2023-08-29 8:58 dpdklab
2023-08-29 6:12 dpdklab
2023-08-28 21:26 dpdklab
2023-08-28 21:07 dpdklab
2023-08-28 20:24 dpdklab
2023-08-28 20:23 dpdklab
2023-08-28 20:22 dpdklab
2023-08-28 20:08 dpdklab
2023-08-28 20:06 dpdklab
2023-08-28 20:05 dpdklab
2023-08-28 20:02 dpdklab
2023-08-28 20:00 dpdklab
2023-08-28 19:59 dpdklab
2023-08-28 19:59 dpdklab
2023-08-28 19:57 dpdklab
2023-08-28 19:54 dpdklab
2023-08-28 19:53 dpdklab
2023-08-28 19:51 dpdklab
2023-08-28 19:50 dpdklab
2023-08-28 19:49 dpdklab
2023-08-28 19:48 dpdklab
2023-08-28 19:46 dpdklab
2023-08-28 19:45 dpdklab
2023-08-28 19:44 dpdklab
2023-08-28 19:43 dpdklab
2023-08-28 19:43 dpdklab
2023-08-28 19:41 dpdklab
2023-08-28 19:40 dpdklab
2023-08-28 19:39 dpdklab
2023-08-28 19:38 dpdklab
2023-08-28 19:36 dpdklab
2023-08-28 19:34 dpdklab
2023-08-28 19:33 dpdklab
2023-08-28 19:33 dpdklab
2023-08-28 19:32 dpdklab
2023-08-28 19:31 dpdklab
2023-08-28 19:31 dpdklab
2023-08-28 19:30 dpdklab
2023-08-28 19:29 dpdklab
2023-08-28 19:28 dpdklab
2023-08-28 19:28 dpdklab
2023-08-28 19:28 dpdklab
2023-08-28 19:28 dpdklab
2023-08-28 19:27 dpdklab
2023-08-28 19:27 dpdklab
2023-08-28 19:27 dpdklab
2023-08-28 19:27 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=64ecfb42.810a0220.2b29f.2fbfSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=anatoly.burakov@intel.com \
--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).