Set timeoutFactor to 20 for RISC-V tests
Open
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
This is based on the suggestion in slack at https://adoptium.slack.com/archives/D02FJ8V16Q6/p1637061299000100?thread_ts=1632900859.002400&cid=D02FJ8V16Q6 - many of the Bisheng11 sanity.openjdk suite tests hit timeouts at the moment.
Contributor guide
Research direction
Start by searching the test configuration for timeoutFactor and the RISC-V test selection used by the sanity.openjdk suite. Confirm how Bisheng11 sanity tests receive their timeout settings; done means RISC-V tests use a factor of 20 and the affected suite no longer hits the reported timeouts.
Written by the indexing model from the issue text.
Assessment
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100