Add @Monster annotation and run these tests periodically [LUCENE-5606]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
We have some awesome very heavy tests, Test2B\*, but they are `@Ignored` and we never run them. I think we should add a new `@Monster` annotation and set up a Jenkins job with huge test timeout, big Java heap, etc.?
---
Migrated from [LUCENE-5606](https://issues.apache.org/jira/browse/LUCENE-5606) by Michael McCandless (@mikemccand), updated Apr 16 2014
Attachments: [LUCENE-5606.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-5606/LUCENE-5606.patch)
Contributor guide
Research direction
Start with the ignored Test2B* tests and the attached LUCENE-5606.patch, then inspect how Lucene currently marks tests and configures Jenkins jobs. Define the @Monster annotation and periodic Jenkins execution with the required timeout and heap settings; done means the heavy tests run in that job without affecting ordinary test runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100