Fix test failure by adjusting dates to match partition range
What does this MR do and why?
Related: https://gitlab.com/gitlab-org/quality/test-failure-issues/-/issues/12725+
The test was failing because it tried to insert a record with date '2025-07-15', which is before the partition range(starts August 1, 2025). When the sync trigger tried to copy this to the partitioned table, it failed because no July partition exists. This MR fixes the test by:
- Changing test data to use dates within the August partition range (starting from 2025-08-01)
- Overriding
START_DATEto 2025-08-10 in the test context to verify the exclusion logic - Ensuring the migration correctly identifies min_id for records on or after START_DATE
References
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Edited by Emma Park