lowRISC / lowRISC/opentitan

[rom_e2e] Revisit the "realtime" timeout for the `rom_e2e_...` tests

Open
#30,999 0 comments 0 reactions 0 assignees View on GitHub
Component:Rom/E2e/Task
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

### Description

All realtime timeout are fairly high (240min & higher). Do we really need timeout which run this long? If one test breaks and somehow don't trigger the simulation timeout the test will run unnecessary long.

Contributor guide

Open the contributing guide

Research direction

Start by locating the realtime timeout configuration used by the rom_e2e tests and reviewing how it relates to the simulation timeout. Determine whether the current 240-minute-or-longer values are necessary, then verify that the selected timeout still allows valid tests to complete while stopping a stalled test sooner.

Written by the indexing model from the issue text.

Assessment

Domain
testing-qa
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.