From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Shunzhi Wen <shunzhi.wen@arm.com>,
dpdk-test-reports@iol.unh.edu, Shunzhi Wen <shunzhi.wen@arm.com>
Subject: |FAILURE| pw142674 [PATCH] eal: add support for TRNG with Arm RNG fe
Date: Wed, 24 Jul 2024 04:54:17 -0700 (PDT) [thread overview]
Message-ID: <66a0eb69.050a0220.3c9dfd.3ee7SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240723212703.721050-1-shunzhi.wen@arm.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/142674
_Testing issues_
Submitter: Shunzhi Wen <shunzhi.wen@arm.com>
Date: Tuesday, July 23 2024 21:27:03
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:82c47f005b9a0a1e3a649664b7713443d18abe43
142674 --> testing issues
Upstream job id: Generic-VM-Unit-Test-DPDK#24325
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | FAIL |
+---------------------+----------------+
| CentOS Stream 9 | PEND |
+---------------------+----------------+
| CentOS Stream 8 | PEND |
+---------------------+----------------+
| Debian Bullseye | PEND |
+---------------------+----------------+
==== Unit test summary for Windows Server 2019 (dpdk_unit_test): ====
Failed to get the unit test results.
Displaying the unit test results is not supported for some environments,
such as our aarch32 testing, where meson is not used to run the tests.
Download the logs available on our CI site.
==== End log output ====
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
Debian Bullseye
Kernel: 5.4.0-167-generic
Compiler: gcc 10.2.1-6
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/30600/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-07-24 11:54 UTC|newest]
Thread overview: 111+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240723212703.721050-1-shunzhi.wen@arm.com>
2024-07-23 21:00 ` |SUCCESS| pw142674 [PATCH] eal: add support for TRNG with Arm RNG feature qemudev
2024-07-23 21:04 ` qemudev
2024-07-23 21:27 ` |WARNING| " checkpatch
2024-07-23 22:23 ` |FAILURE| " 0-day Robot
2024-07-24 8:30 ` |PENDING| pw142674 [PATCH] eal: add support for TRNG with Arm RNG fe dpdklab
2024-07-24 8:33 ` dpdklab
2024-07-24 8:43 ` |SUCCESS| " dpdklab
2024-07-24 8:46 ` dpdklab
2024-07-24 9:01 ` dpdklab
2024-07-24 9:06 ` dpdklab
2024-07-24 9:14 ` dpdklab
2024-07-24 9:20 ` dpdklab
2024-07-24 9:23 ` dpdklab
2024-07-24 9:24 ` dpdklab
2024-07-24 9:28 ` dpdklab
2024-07-24 9:28 ` dpdklab
2024-07-24 9:31 ` dpdklab
2024-07-24 9:33 ` dpdklab
2024-07-24 9:33 ` |PENDING| " dpdklab
2024-07-24 9:38 ` dpdklab
2024-07-24 9:41 ` dpdklab
2024-07-24 9:43 ` dpdklab
2024-07-24 9:43 ` dpdklab
2024-07-24 9:43 ` dpdklab
2024-07-24 9:44 ` dpdklab
2024-07-24 9:45 ` dpdklab
2024-07-24 9:46 ` dpdklab
2024-07-24 9:47 ` dpdklab
2024-07-24 9:47 ` dpdklab
2024-07-24 9:48 ` dpdklab
2024-07-24 9:50 ` dpdklab
2024-07-24 9:53 ` |SUCCESS| " dpdklab
2024-07-24 9:54 ` dpdklab
2024-07-24 10:06 ` dpdklab
2024-07-24 10:34 ` dpdklab
2024-07-24 11:38 ` |FAILURE| " dpdklab
2024-07-24 11:40 ` dpdklab
2024-07-24 11:42 ` dpdklab
2024-07-24 11:43 ` dpdklab
2024-07-24 11:44 ` dpdklab
2024-07-24 11:44 ` dpdklab
2024-07-24 11:44 ` |PENDING| " dpdklab
2024-07-24 11:50 ` dpdklab
2024-07-24 11:54 ` dpdklab [this message]
2024-07-24 12:18 ` |FAILURE| " dpdklab
2024-07-24 12:21 ` |PENDING| " dpdklab
2024-07-24 12:25 ` dpdklab
2024-07-24 12:29 ` dpdklab
2024-07-24 12:37 ` |FAILURE| " dpdklab
2024-07-24 12:37 ` dpdklab
2024-07-24 12:40 ` dpdklab
2024-07-24 12:47 ` dpdklab
2024-07-24 12:48 ` dpdklab
2024-07-24 12:51 ` dpdklab
2024-07-24 12:51 ` |PENDING| " dpdklab
2024-07-24 12:51 ` |FAILURE| " dpdklab
2024-07-24 12:52 ` |PENDING| " dpdklab
2024-07-24 12:53 ` dpdklab
2024-07-24 12:55 ` |FAILURE| " dpdklab
2024-07-24 12:55 ` dpdklab
2024-07-24 12:57 ` |PENDING| " dpdklab
2024-07-24 12:58 ` |FAILURE| " dpdklab
2024-07-24 12:59 ` |PENDING| " dpdklab
2024-07-24 12:59 ` |FAILURE| " dpdklab
2024-07-24 12:59 ` dpdklab
2024-07-24 13:05 ` dpdklab
2024-07-24 13:05 ` |PENDING| " dpdklab
2024-07-24 13:05 ` |FAILURE| " dpdklab
2024-07-24 13:11 ` dpdklab
2024-07-24 13:11 ` dpdklab
2024-07-24 13:11 ` dpdklab
2024-07-24 13:12 ` |PENDING| " dpdklab
2024-07-24 13:13 ` dpdklab
2024-07-24 13:14 ` |FAILURE| " dpdklab
2024-07-24 13:16 ` |PENDING| " dpdklab
2024-07-24 13:20 ` dpdklab
2024-07-24 13:20 ` dpdklab
2024-07-24 13:21 ` |FAILURE| " dpdklab
2024-07-24 13:22 ` |PENDING| " dpdklab
2024-07-24 13:22 ` dpdklab
2024-07-24 13:23 ` dpdklab
2024-07-24 13:24 ` dpdklab
2024-07-24 13:25 ` |FAILURE| " dpdklab
2024-07-24 13:26 ` dpdklab
2024-07-24 13:29 ` dpdklab
2024-07-24 13:31 ` |PENDING| " dpdklab
2024-07-24 13:32 ` dpdklab
2024-07-24 13:32 ` dpdklab
2024-07-24 13:34 ` |FAILURE| " dpdklab
2024-07-24 13:35 ` |PENDING| " dpdklab
2024-07-24 13:36 ` |FAILURE| " dpdklab
2024-07-24 13:36 ` dpdklab
2024-07-24 13:39 ` |PENDING| " dpdklab
2024-07-24 13:41 ` |FAILURE| " dpdklab
2024-07-24 13:42 ` |SUCCESS| " dpdklab
2024-07-24 13:47 ` dpdklab
2024-07-24 13:47 ` |FAILURE| " dpdklab
2024-07-24 13:49 ` |PENDING| " dpdklab
2024-07-24 13:51 ` dpdklab
2024-07-24 13:51 ` |FAILURE| " dpdklab
2024-07-24 13:51 ` |PENDING| " dpdklab
2024-07-24 13:54 ` |FAILURE| " dpdklab
2024-07-24 13:57 ` dpdklab
2024-07-24 14:07 ` |PENDING| " dpdklab
2024-07-24 14:12 ` dpdklab
2024-07-24 14:21 ` dpdklab
2024-07-24 14:24 ` dpdklab
2024-07-24 14:44 ` dpdklab
2024-07-24 14:48 ` dpdklab
2024-07-24 14:51 ` |SUCCESS| " dpdklab
2024-07-25 17:05 ` 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=66a0eb69.050a0220.3c9dfd.3ee7SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=shunzhi.wen@arm.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).