From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |PENDING| pw152345 [PATCH] app/crypto-perf: avoid infinite loop
Date: Wed, 12 Mar 2025 09:46:05 -0700 (PDT) [thread overview]
Message-ID: <67d1ba4d.050a0220.27a73f.064aSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250311155850.1043336-1-rchiluka@marvell.com>
Test-Label: iol-compile-amd64-testing
Test-Status: PENDING
http://dpdk.org/patch/152345
_Testing pending_
Submitter: Rupesh Chiluka <rchiluka@marvell.com>
Date: Tuesday, March 11 2025 15:58:50
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:57c3c8f4f18d65f6b09057819ba36532f2f5e04c
152345 --> testing pending
Upstream job id: Generic-DPDK-Compile-Meson#371490
Test environment and result as below:
+------------------+--------------------+-------------------+------------------+
| Environment | dpdk_meson_compile | dpdk_compile_spdk | dpdk_compile_ovs |
+==================+====================+===================+==================+
| CentOS Stream 9 | PEND | PEND | SKIPPED |
+------------------+--------------------+-------------------+------------------+
| CentOS Stream 10 | PASS | SKIPPED | SKIPPED |
+------------------+--------------------+-------------------+------------------+
| Debian 12 | PEND | PEND | SKIPPED |
+------------------+--------------------+-------------------+------------------+
| Fedora 40 | PEND | PEND | SKIPPED |
+------------------+--------------------+-------------------+------------------+
| Fedora 41 | PEND | PEND | PEND |
+------------------+--------------------+-------------------+------------------+
CentOS Stream 9
Kernel: Depends on container host
Compiler: gcc 11.5.0 20240719 (Red Hat 11.5.0-2)
CentOS Stream 10
Kernel: Depends on container host
Compiler: gcc 14.2.1 20241104 (Red Hat 14.2.1-6)
Debian 12
Kernel: Depends on container host
Compiler: gcc (Debian 12.2.0-14) 12.2.0
Fedora 40
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
Fedora 41
Kernel: Depends on container host
Compiler: gcc 14.2.1 20240912 (Red Hat 14.2.1-3)
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/32807/
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:[~2025-03-12 16:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250311155850.1043336-1-rchiluka@marvell.com>
2025-03-12 10:19 ` |SUCCESS| " qemudev
2025-03-12 10:23 ` qemudev
2025-03-12 10:52 ` checkpatch
2025-03-12 14:15 ` dpdklab
2025-03-12 14:23 ` dpdklab
2025-03-12 14:25 ` dpdklab
2025-03-12 14:25 ` dpdklab
2025-03-12 14:34 ` dpdklab
2025-03-12 14:38 ` dpdklab
2025-03-12 14:57 ` dpdklab
2025-03-12 15:04 ` dpdklab
2025-03-12 15:12 ` dpdklab
2025-03-12 16:35 ` |PENDING| " dpdklab
2025-03-12 16:46 ` dpdklab [this message]
2025-03-12 16:47 ` |SUCCESS| " dpdklab
2025-03-12 16:49 ` dpdklab
2025-03-12 17:02 ` dpdklab
2025-03-12 17:02 ` |PENDING| " dpdklab
2025-03-12 17:02 ` |SUCCESS| " dpdklab
2025-03-12 17:28 ` dpdklab
2025-03-12 17:44 ` dpdklab
2025-03-12 17:45 ` dpdklab
2025-03-12 18:37 ` dpdklab
2025-03-12 18:37 ` dpdklab
2025-03-12 19:01 ` dpdklab
2025-03-12 19:44 ` dpdklab
2025-03-12 19:52 ` 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=67d1ba4d.050a0220.27a73f.064aSMTPIN_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).