Nightly cassert failures (2026-09-11)
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/34557487530
Failing jobs:
- cassert PG17 - regress
New failures not previously tracked:
- cassert PG17 - 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 cassert PG17 - regress job logs to locate the assertion failures and determine which are new. Compare them with the existing tracked failures; done means the new failure is explained and either corrected or documented as a pre-existing PG-core or Citus assertion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, github-actions, 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