some nightly tests take hours [LUCENE-3994]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
The nightly builds are taking 4-7 hours.
This is caused by a few bad apples (can be seen https://builds.apache.org/job/Lucene-trunk/1896/testReport/).
The top 5 are (all in analysis):
- TestSynonymMapFilter: 1 hr 54 min
- TestRandomChains: 1 hr 22 min
- TestRemoveDuplicatesTokenFilter: 32 min
- TestMappingCharFilter: 28 min
- TestWordDelimiterFilter: 22 min
so thats 4.5 hours right there for that run....
---
Migrated from [LUCENE-3994](https://issues.apache.org/jira/browse/LUCENE-3994) by Robert Muir (@rmuir), updated May 09 2016
Attachments: [LUCENE-3994.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-3994/LUCENE-3994.patch)
Contributor guide
Research direction
Start with the linked Lucene trunk test report and the five named analysis tests: TestSynonymMapFilter, TestRandomChains, TestRemoveDuplicatesTokenFilter, TestMappingCharFilter, and TestWordDelimiterFilter. Review the attached LUCENE-3994.patch for prior context, then verify that the identified nightly-test bottlenecks no longer account for hours of build time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100