[DPDK/core Bug 1558] 10 second timeout is too short to pass tests on RISC-V devices.

[DPDK/core Bug 1558] 10 second timeout is too short to pass tests on RISC-V devices.

[bugzilla]

[-- 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 --]

[DPDK/core Bug 1558] 10 second timeout is too short to pass tests on RISC-V devices.

[bugzilla]

[-- 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 --]