Ticket #939 (closed defect: fixed)
scheduler_changes accumulates data for Nightly schedulers when onlyIfChanged is False
|Reported by:||catlee||Owned by:||catlee|
Changes are inserted into the scheduler_changes table for processing via classify_changes, but are only retired if onlyIfChanged is True.
If onlyIfChanged is False, the rows will stay around forever. We've got 3.4 million rows in this table after running for a few months.
Fix should be simple, have the Nightly scheduler (and other timed schedulers?) avoid calling classify_changes if onlyIfChanged is False, or have it clear out any accumulated changes when it starts a build.