Integration Tests Broken/Flaky in TravisCI
- Dominant language
- Java
- Stars
- 14.1k
- Forks
- 3.8k
- Avg merge
- 2d 58m
- Merged PRs (30d)
- 233
Description
### Affected Version
master branch
### Description
I'm sure others have noticed but I don't see any dedicated issue for tracking as of yet so I wanted to get this up there for discussion/tracking
failures seem pretty common for the following Travis modules lately:
* transactional kafka index integration test slow
* kafka index integration tests with various formats
* perfect rollup parallel batch index integration test
I have just begun looking at it so I am not sure if the tests are actually broken or if there is some resources/timing issues, etc. If anyone has started looking into this too, please add your findings!
Contributor guide
Research direction
Start with the TravisCI runs for the transactional Kafka index integration test, Kafka index integration tests with various formats, and perfect rollup parallel batch index integration test. Compare their failure output and timing to determine whether the tests are broken or affected by resource contention. Done means identifying the cause and stabilizing the affected integration tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, kafka
- Domain
- ci-cd, data-engineering, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100