You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix flaky rollup test by stopping jobs before index cleanup
The test was flaky because rollup job coroutines continued running after
test cleanup, causing a race condition where the config index was recreated
with incorrect dynamic mappings.
Root cause:
- Tests create enabled rollups -> JobScheduler schedules them
- RollupRunner.runJob() launches coroutines via launch {}
- Test @after wipes indices
- BUT coroutines are still running in background
- Coroutines write metadata AFTER indices wiped
- Index auto-creates with wrong dynamic mappings (long vs date)
- Next test fails with mapping conflict on rollup_metadata.continuous.next_window_end_time
Signed-off-by: bowenlan-amzn <bowenlan23@gmail.com>
0 commit comments