Nightly cassert failures (2026-09-14)
Open
nightly-cassert
- Dominant language
- C
- Stars
- 12.8k
- Forks
- 794
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 31
Description
Nightly full-cassert run failed.
Run: https://github.com/citusdata/citus/actions/runs/34801817386
Failing jobs:
- cassert PG17 - regress
- cassert PG19 - regress
New failures not previously tracked:
- cassert PG19 - regress
First runs are EXPECTED red as pre-existing PG-core and Citus asserts surface.
Contributor guide
Research direction
Start with the linked GitHub Actions run and inspect the failing cassert PG17 and PG19 regress jobs. Compare the new PG19 failure with previously tracked cassert failures and identify whether it is a PG-core or Citus assertion. Done means the cause is resolved or the failure is explicitly tracked, with the relevant regress jobs passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, postgresql
- Domain
- ci-cd, databases, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100