test: the divergence record is compared without its refreshed 'at' (keel#129) #130

Merged

marcos-mendez merged 1 commit from test/divergence-record-clock-second into main

2026-10-09 14:37:15 -03:00

marcos-mendez commented

2026-10-09 13:58:27 -03:00

(Migrated from github.com)

Closes #129.

keel.system.dbfollow._diverged rewrites the record's at on every run (it is when the divergence was last seen). The test read the record, ran follow a second time, and compared the whole dict — a clock-second boundary between the runs failed it on CI (16:52:31Z vs 16:52:32Z, tests / coverage on 2026-10-09).

The comparison now covers errant and holder, which is what the test means: the record's content stays stable and the second run alerts no more (that part is asserted separately).

Tests only; no changelog entry.

Closes #129. `keel.system.dbfollow._diverged` rewrites the record's `at` on every run (it is when the divergence was last seen). The test read the record, ran `follow` a second time, and compared the whole dict — a clock-second boundary between the runs failed it on CI (16:52:31Z vs 16:52:32Z, tests / coverage on 2026-10-09). The comparison now covers `errant` and `holder`, which is what the test means: the record's content stays stable and the second run alerts no more (that part is asserted separately). Tests only; no changelog entry.