From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: Akhil Goyal <gakhil@marvell.com>,
dpdk-test-reports@iol.unh.edu, Akhil Goyal <gakhil@marvell.com>
Subject: |FAILURE| pw140270 [PATCH] test/crypto: fix enqueue dequeue callback
Date: Wed, 22 May 2024 07:48:59 -0700 (PDT) [thread overview]
Message-ID: <664e05db.050a0220.1a14c.60bbSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240522134835.3453044-1-gakhil@marvell.com>
Test-Label: iol-unit-amd64-testing
Test-Status: FAILURE
http://dpdk.org/patch/140270
_Testing issues_
Submitter: Akhil Goyal <gakhil@marvell.com>
Date: Wednesday, May 22 2024 13:48:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:6f80df8cb0f889203d7cd27766abcc6ebc720e33
140270 --> testing fail
Test environment and result as below:
+---------------------+----------------+
| Environment | dpdk_unit_test |
+=====================+================+
| Windows Server 2019 | PASS |
+---------------------+----------------+
| CentOS Stream 8 | FAIL |
+---------------------+----------------+
| CentOS Stream 9 | FAIL |
+---------------------+----------------+
| Debian Bullseye | FAIL |
+---------------------+----------------+
==== 20 line log output for Debian Bullseye (dpdk_unit_test): ====
Windows Server 2019
Kernel: 10.0.17763
Compiler: clang 14.0 and gcc 8.1.0 (MinGW)
CentOS Stream 8
Kernel: 5.4.0-167-generic
Compiler: gcc 8.5.0 20210514
CentOS Stream 9
Kernel: 5.4.0-167-generic
Compiler: gcc 11.4.1 20230605
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/29988/
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-05-22 14:49 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240522134835.3453044-1-gakhil@marvell.com>
2024-05-22 13:21 ` |SUCCESS| pw140270 [PATCH] test/crypto: fix enqueue dequeue callback case qemudev
2024-05-22 13:26 ` qemudev
2024-05-22 13:49 ` |WARNING| " checkpatch
2024-05-22 14:33 ` |SUCCESS| pw140270 [PATCH] test/crypto: fix enqueue dequeue callback dpdklab
2024-05-22 14:34 ` dpdklab
2024-05-22 14:35 ` dpdklab
2024-05-22 14:36 ` dpdklab
2024-05-22 14:37 ` dpdklab
2024-05-22 14:37 ` dpdklab
2024-05-22 14:37 ` dpdklab
2024-05-22 14:38 ` dpdklab
2024-05-22 14:38 ` dpdklab
2024-05-22 14:39 ` dpdklab
2024-05-22 14:40 ` dpdklab
2024-05-22 14:40 ` dpdklab
2024-05-22 14:41 ` dpdklab
2024-05-22 14:42 ` dpdklab
2024-05-22 14:43 ` dpdklab
2024-05-22 14:44 ` |FAILURE| " dpdklab
2024-05-22 14:44 ` |SUCCESS| pw140270 [PATCH] test/crypto: fix enqueue dequeue callback case 0-day Robot
2024-05-22 14:44 ` |SUCCESS| pw140270 [PATCH] test/crypto: fix enqueue dequeue callback dpdklab
2024-05-22 14:44 ` dpdklab
2024-05-22 14:45 ` dpdklab
2024-05-22 14:45 ` dpdklab
2024-05-22 14:45 ` dpdklab
2024-05-22 14:45 ` |FAILURE| " dpdklab
2024-05-22 14:46 ` dpdklab
2024-05-22 14:46 ` |SUCCESS| " dpdklab
2024-05-22 14:46 ` dpdklab
2024-05-22 14:46 ` |FAILURE| " dpdklab
2024-05-22 14:47 ` |SUCCESS| " dpdklab
2024-05-22 14:47 ` dpdklab
2024-05-22 14:48 ` dpdklab
2024-05-22 14:48 ` dpdklab
2024-05-22 14:48 ` dpdklab
2024-05-22 14:48 ` dpdklab [this message]
2024-05-22 14:49 ` dpdklab
2024-05-22 14:49 ` dpdklab
2024-05-22 14:49 ` dpdklab
2024-05-22 14:49 ` dpdklab
2024-05-22 14:49 ` |FAILURE| " dpdklab
2024-05-22 14:50 ` dpdklab
2024-05-22 14:50 ` |SUCCESS| " dpdklab
2024-05-22 14:50 ` dpdklab
2024-05-22 14:50 ` dpdklab
2024-05-22 14:51 ` dpdklab
2024-05-22 14:51 ` |FAILURE| " dpdklab
2024-05-22 14:51 ` |SUCCESS| " dpdklab
2024-05-22 14:51 ` dpdklab
2024-05-22 14:51 ` dpdklab
2024-05-22 14:52 ` dpdklab
2024-05-22 14:52 ` dpdklab
2024-05-22 14:52 ` dpdklab
2024-05-22 14:52 ` |FAILURE| " dpdklab
2024-05-22 14:52 ` |SUCCESS| " dpdklab
2024-05-22 14:52 ` |FAILURE| " dpdklab
2024-05-22 14:53 ` |SUCCESS| " dpdklab
2024-05-22 14:53 ` |FAILURE| " dpdklab
2024-05-22 14:53 ` |SUCCESS| " dpdklab
2024-05-22 14:53 ` |FAILURE| " dpdklab
2024-05-22 14:53 ` |SUCCESS| " dpdklab
2024-05-22 14:53 ` dpdklab
2024-05-22 14:54 ` dpdklab
2024-05-22 14:54 ` dpdklab
2024-05-22 14:54 ` |FAILURE| " dpdklab
2024-05-22 14:54 ` dpdklab
2024-05-22 14:54 ` dpdklab
2024-05-22 14:54 ` |SUCCESS| " dpdklab
2024-05-22 14:54 ` dpdklab
2024-05-22 14:55 ` |FAILURE| " dpdklab
2024-05-22 14:56 ` dpdklab
2024-05-22 14:57 ` dpdklab
2024-05-22 15:00 ` dpdklab
2024-05-22 15:00 ` dpdklab
2024-05-22 15:03 ` dpdklab
2024-05-22 15:03 ` dpdklab
2024-05-22 15:06 ` dpdklab
2024-05-22 15:06 ` |SUCCESS| " dpdklab
2024-05-22 15:08 ` |FAILURE| " dpdklab
2024-05-22 15:10 ` |SUCCESS| " dpdklab
2024-05-22 15:11 ` |FAILURE| " dpdklab
2024-05-22 15:12 ` |SUCCESS| " dpdklab
2024-05-22 15:22 ` |FAILURE| " dpdklab
2024-05-22 15:25 ` |SUCCESS| " dpdklab
2024-05-22 15:59 ` dpdklab
2024-05-22 18:04 ` dpdklab
2024-05-23 6:09 ` 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=664e05db.050a0220.1a14c.60bbSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=gakhil@marvell.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).