Skip to content

chore: implement phase 11 - #2789

Draft
Tofel wants to merge 1 commit into
dx-5122-alerts-assertion-p10from
dx-5122-alerts-assertion-p11
Draft

chore: implement phase 11#2789
Tofel wants to merge 1 commit into
dx-5122-alerts-assertion-p10from
dx-5122-alerts-assertion-p11

Conversation

@Tofel

@Tofel Tofel commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Add coverage.go's declared-KeepLast check (no_data_state/exec_err_state,
not just an observed reason) and close the remaining §22 gaps: newly_bad's
no-early-exit clock assertion, a recorder-mode gap right after the deploy,
a rule's own coverage gap overriding its own recovery, a genuinely
skew-discriminating staleness test, exit-2 consequences on two
Reason-only coverage tests, and end-to-end checks for log-name
collapse, a truncated log, and the real watch-written state histogram.


Stack created with GitHub Stacks CLIGive Feedback 💬

@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown

📊 API Diff Results

No changes detected for module github.com/smartcontractkit/chainlink-testing-framework/grafana-alertcheck

View full report

@Tofel
Tofel force-pushed the dx-5122-alerts-assertion-p11 branch from 658d3de to ea8e035 Compare September 1, 2026 11:25
@Tofel
Tofel force-pushed the dx-5122-alerts-assertion-p11 branch from ea8e035 to 44ded19 Compare September 1, 2026 14:18
@Tofel
Tofel force-pushed the dx-5122-alerts-assertion-p11 branch from 44ded19 to 3efbb2f Compare September 1, 2026 14:46
@Tofel
Tofel force-pushed the dx-5122-alerts-assertion-p11 branch 2 times, most recently from 7a0caf2 to ceb8796 Compare September 2, 2026 09:45
@Tofel
Tofel force-pushed the dx-5122-alerts-assertion-p11 branch from ceb8796 to c8f7e00 Compare September 2, 2026 09:57
@Tofel
Tofel force-pushed the dx-5122-alerts-assertion-p11 branch from c8f7e00 to df94923 Compare September 2, 2026 11:05
Add coverage.go's declared-KeepLast check (no_data_state/exec_err_state,
not just an observed reason) and close the remaining §22 gaps: newly_bad's
no-early-exit clock assertion, a recorder-mode gap right after the deploy,
a rule's own coverage gap overriding its own recovery, a genuinely
skew-discriminating staleness test, exit-2 consequences on two
Reason-only coverage tests, and end-to-end checks for log-name
collapse, a truncated log, and the real watch-written state histogram.
@Tofel
Tofel force-pushed the dx-5122-alerts-assertion-p11 branch from df94923 to 159d0b6 Compare September 2, 2026 11:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant