Reproduce flaky e2e test failures in Amber
Open
- Dominant language
- Scala
- Stars
- 314
- Forks
- 187
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 214
Description
### Task Summary
As mentioned in #3880, for a permanent fix of `DataProcessingSpec` and `PauseSpec` timeout issues, we need to find a way to stably reproduce the problem outside of the CI environment in order to find the root cause.
### Priority
P2 – Medium
### Task Type
- [ ] Code Implementation
- [ ] Documentation
- [ ] Refactor / Cleanup
- [x] Testing / QA
- [ ] DevOps / Deployment
Contributor guide
Research direction
Start by reading the context in #3880 and the e2e tests named DataProcessingSpec and PauseSpec. Run those tests outside the CI environment and investigate whether their timeout failures can be reproduced reliably. Done means documenting a stable reproduction path that can support a permanent fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100