From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw132299 [PATCH] random: clarify PRNG MT safety guarantees
Date: Wed, 04 Oct 2023 07:46:37 -0700 (PDT) [thread overview]
Message-ID: <651d7acd.810a0220.ba118.8e67SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-compile-arm64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/132299
_Testing PASS_
Submitter: Mattias Ronnblom <mattias.ronnblom@ericsson.com>
Date: Wednesday, October 04 2023 10:54:49
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:687a5b12b14f02f0d3624f4b36b34dba8119a680
132299 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Fedora 38 (ARM Clang) | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Fedora 38 (ARM Clang)
Kernel: Depends on container host
Compiler: clang 16.0.3
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/27822/
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-04 14:46 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 14:46 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-04 15:12 dpdklab
2023-10-04 15:08 dpdklab
2023-10-04 15:05 dpdklab
2023-10-04 15:04 dpdklab
2023-10-04 15:04 dpdklab
2023-10-04 15:04 dpdklab
2023-10-04 15:00 dpdklab
2023-10-04 15:00 dpdklab
2023-10-04 14:59 dpdklab
2023-10-04 14:59 dpdklab
2023-10-04 14:58 dpdklab
2023-10-04 14:56 dpdklab
2023-10-04 14:50 dpdklab
2023-10-04 14:48 dpdklab
2023-10-04 14:46 dpdklab
2023-10-04 14:45 dpdklab
2023-10-04 14:39 dpdklab
2023-10-04 14:35 dpdklab
2023-10-04 14:28 dpdklab
2023-10-04 14:26 dpdklab
2023-10-04 14:26 dpdklab
2023-10-04 14:22 dpdklab
2023-10-04 14:19 dpdklab
2023-10-04 14:15 dpdklab
2023-10-04 14:14 dpdklab
2023-10-04 14:08 dpdklab
2023-10-04 14:07 dpdklab
2023-10-04 14:02 dpdklab
2023-10-04 13:58 dpdklab
2023-10-04 13:51 dpdklab
2023-10-04 13:50 dpdklab
2023-10-04 13:48 dpdklab
2023-10-04 13:47 dpdklab
2023-10-04 13:47 dpdklab
2023-10-04 13:41 dpdklab
2023-10-04 13:35 dpdklab
2023-10-04 13:34 dpdklab
2023-10-04 13:32 dpdklab
2023-10-04 13:30 dpdklab
2023-10-04 13:29 dpdklab
2023-10-04 13:26 dpdklab
2023-10-04 13:26 dpdklab
2023-10-04 13:26 dpdklab
2023-10-04 13:26 dpdklab
2023-10-04 13:25 dpdklab
[not found] <20231004105449.367667-1-mattias.ronnblom@ericsson.com>
2023-10-04 10:42 ` qemudev
2023-10-04 10:46 ` qemudev
2023-10-04 11:01 ` checkpatch
2023-10-04 12:19 ` 0-day Robot
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=651d7acd.810a0220.ba118.8e67SMTPIN_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).