Skip to content

Test report severity planning paths against PostgreSQL - #3206

Draft
clawosiris wants to merge 1 commit into
stack/pr-3081-report-severity-planningfrom
test/pr-3081-report-severity-coverage
Draft

clawosiris wants to merge 1 commit into
stack/pr-3081-report-severity-planningfrom
test/pr-3081-report-severity-coverage

Conversation

@clawosiris

Copy link
Copy Markdown
Contributor

Summary

  • run the report-severity functions against a live PostgreSQL fixture
  • cover valid, absent, NULL, expired, and key-mismatched cache entries
  • cover dynamic severity and overrides on/off, min-QoD filtering, NULL result types, and empty results
  • verify all three split functions are installed as STABLE
  • prove the dynamic branch is skipped on a cache hit and invoked on a cache miss

This is stacked on #3081. The temporary base branch mirrors its current head exactly so this PR contains only the coverage commit; it can be retargeted to main after #3081 merges.

@TheBeast85, this adds the database-backed regression coverage discussed in the review of #3081.

Validation

  • focused PostgreSQL CTest passes against PostgreSQL 17
  • full Debug build passes, including manage_pg.c
  • CMake formatting and diff hygiene checks pass

Agent: GEA
Model: openai/gpt-5.6-sol
Thinking: xhigh
Bot-Owner: @llunved

Cover cached and computed report severity behavior against PostgreSQL, including the lazy dynamic fallback introduced by PR #3081.

Agent: GEA
Model: openai/gpt-5.6-sol
Thinking: xhigh
Bot-Owner: @llunved
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