ci_tier_check: accepted limits (matrix include/exclude, run-script expressions, aggregator || true, schedule) — fix only if seen in practice
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
The issue describes edge cases in the CI tier checker script at tools/ci_tier_check.sh. Start by understanding the script's logic and the specific GitHub Actions constructs it validates (matrix includes/excludes, run-script expressions, aggregators, schedules). Review the linked PR #1273 and issue #1275 for context. 'Done' means adding detection for one of these patterns only if it appears in a real workflow, not preemptively.
Written by the indexing model from the issue text.
Description
Accepted limits of tools/ci_tier_check.sh after #1273, filed per the out-of-scope and one-layer rules (#1275). Each is a constructed mutant of the checker, and none has an instance in the real workflows today. Fix one only if it ever occurs in practice; until then, code review covers it.
- Matrix
include/exclude: aninclude: [{os: macos-15-intel}]adds a leg that is not required and is not flagged (the original #1264 macOS shape); anexcludeof a required leg means that check never reports. Repro: /tmp/astra-1264A-r2/ round-2 evidence (see #1273). - The stale-waiver check (step-output waivers pinned by hash) has no selftest plant.
${{ }}expressions insiderun:scripts,runs-onandcontainerare not judged.- An aggregator whose script ignores a failed worker (
|| true), and aschedule:trigger on ci.yml: code-review concerns by design (#1273 round-2 scope cut).
- Dominant language
- C
- Stars
- 3
- Forks
- 7
- Avg merge
- 3h 56m
- Merged PRs (30d)
- 102
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from InauguralSystems/EigenScript
-
area:lint-tooling bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
InauguralSystems/EigenScript#1340 ·
Maintainers usually reply within 1 day
-
area:stdlib found-by:code-review kind:silent-wrong
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
InauguralSystems/EigenScript#1338 ·
Maintainers usually reply within 1 day
-
area:lint-tooling found-by:critic kind:docs-drift
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
InauguralSystems/EigenScript#1335 ·
Maintainers usually reply within 1 day
-
area:ci found-by:critic kind:gate-defect
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
InauguralSystems/EigenScript#1311 ·
Maintainers usually reply within 1 day
-
enrolment: decide test_gc_runner_controls.py (exempt vs enrol) and whether floors need a ratchetOpenarea:gates found-by:critic kind:decision
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
InauguralSystems/EigenScript#1280 · 1 comment ·
Maintainers usually reply within 1 day
All issues in InauguralSystems/EigenScript
Similar issues
-
[Bug]: chunk_span_bounds and _validated_chunk_spans reject Pydantic models ChunkSpan and AudioFileOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
BasedHardware/omi#19047 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
obsproject/obs-studio#13936 · 2 comments ·
Maintainers usually reply within 1 day
-
category:port-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day