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: Sat, 05 Oct 2024 10:09:33 +0000 [thread overview]
Message-ID: <bug-1558-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1558
Bug ID: 1558
Summary: 10 second timeout is too short to pass tests on RISC-V
devices.
Product: DPDK
Version: 24.07
Hardware: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: i@rain.cx
Target Milestone: ---
I am trying to build dpdk on a RISC-V device.
There are three timeouts:
23/77 DPDK:fast-tests / eventdev_selftest_sw
64/77 DPDK:fast-tests / spinlock_autotest
66/77 DPDK:fast-tests / table_autotest
My device is SOPHON SG2042, the fastest RISC-V device now, it needs at least 20
seconds to pass these 3 tests.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 2768 bytes --]
next reply other threads:[~2024-10-05 10:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-05 10:09 bugzilla [this message]
2024-10-14 13:55 ` [DPDK/core Bug 1558] 10 second timeout is too short to pass tests on RISC-V devices bugzilla
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@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.