From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1558] 10 second timeout is too short to pass tests on RISC-V devices.
Date: Mon, 14 Oct 2024 13:55:00 +0000 [thread overview]
Message-ID: <bug-1558-3-YsccKSq9ED@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1558-3@http.bugs.dpdk.org/>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1558
Kevin Traynor (ktraynor@redhat.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ktraynor@redhat.com
Resolution|--- |WONTFIX
Status|UNCONFIRMED |RESOLVED
--- Comment #3 from Kevin Traynor (ktraynor@redhat.com) ---
I would guess probably unlikely as it for the fast tests, and it could have an
impact on CI, test times etc. but if you believe it should be done, then best
approach is to send a patch and let it be discussed on the dpdk mailing list.
I will close the Bz for now as there is a known workaround available.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3047 bytes --]
prev parent reply other threads:[~2024-10-14 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 10:09 bugzilla
2024-10-14 13:55 ` bugzilla [this message]
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=bug-1558-3-YsccKSq9ED@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@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).