Investigate a migration re-check whose control test failed
A migration compatibility result requires a useful comparison with the application on the base schema. When the control fails, the test cannot attribute the failure to the proposed schema change.
Check both runs of the test#
Open the migration finding’s Re-verification entry at the relevant head and read the reason beside the test path. A failure on the base schema differs from a failure on the migrated schema. A failure followed by a pass on a fresh copy is recorded separately as a flaky result.
Investigate the control failure or instability in the test environment, then inspect a later re-check. A failed control alone establishes neither a migration defect nor a verified fix.