re-enable test timeout, but factor in nightly, multiplier, clover [LUCENE-4301]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
Having a test timeout is great (for things like test hangs), but its going to cause a lot of failed builds until we factor in the various flags that can cause tests to run longer, or enable longer-running tests.
Its hard to say what the limits should be since jenkins history is pretty limited at the moment (only 2 nightly runs history available)
---
Migrated from [LUCENE-4301](https://issues.apache.org/jira/browse/LUCENE-4301) by Robert Muir (@rmuir), updated Aug 13 2012
Attachments: [evil.jpg](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-4301/evil.jpg)
Contributor guide
Research direction
Start by locating the test-timeout configuration and the handling of the nightly, multiplier, and clover flags. Review the limited Jenkins history to establish suitable timeout limits; done means timeouts are enabled without causing expected longer-running builds to fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100