No reviewers
Labels
No labels
code-review
correctness
dos
performance
security
severity/high
severity/low
severity/medium
tech-debt
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
h-dv/code-index!325
Loading…
Reference in a new issue
No description provided.
Delete branch "p2-per-package-ci"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Phase 2 of #318, plus the #314 fix behind nightly run 5754's failure.
Phase 2
code-index-first-party-tests. It holds every package-self suite: provenance, digest equals pack, grammar copy, name section, builder paths, rebuild with byte compare, declared profile. It also holds one<lang>_language_overheadper language. Host CI excludes the crate, on both Linux and Windows..forgejo/workflows/package-ci.yml.package (<name>). Each leg runs only when thechangesjob puts it in scope; an empty scope fails open and runs every leg.COSI_PACKAGE), corpus suites and builtin parity. The parity step checks semantics only on each push and enforces both budgets nightly.ci_changes.shroutes package paths to package legs:tests/packages/<name>/**,tables/<name>.rsorcrates/guest/<name>runs only that package's leg, and no host jobs;ci_path_gatingchecks each of these cases on a temporary repo.host_reads_no_live_package: the allowlist shrinks to 1 Phase 3 row, 3 Phase 4 rows and 3 data rows.#314
tests/phase2_acceptance.pybuilds every child process environment through one helper,child_env, which removesCOSI_CORPUS_DIR. The ci.yml step also unsets it.code_index_test_support::product::commandis now the only way a test spawns a binary that can reach the MCP server. 52 call sites in 14 files use it. A registry test,mcp_spawn_registry, enforces this.Verified
ci_path_gating33/33,host_reads_no_live_package5/5,version_site_registry8/8,grammar_provenance7/7,mcp_spawn_registry3/3,frozen_pins3/3,release_notes_quoting2/2.the_door_removes_the_variable_the_server_readsred..code-indexdirectory is left in the corpus.Expected red
package (python)fails its builtin-parity step on python-flask with the #315 delta. That gap was never measured before, because nightly CI died earlier at the #314 contamination guard.#315 is not fixable package-only:
python_imports.rs(the denied-refs list andfilter_layout_targets).Known gap (Phase 4)
package-release.yml'sREQUIRED_JOBSstill lists host jobs. So a package-only commit, whose host jobs are all skipped, cannot be released without a full dispatch.🤖 Generated with Claude Code
https://claude.ai/code/session_0126PDDLB4wNHxKXvWM1VNmu
The first PR run of package-ci.yml failed in 0 s with no job: Forgejo parses a step's continue-on-error as a bool, and a `${{ }}` there is a string ("cannot unmarshal !!str into bool"). The nightly needs no continue-on-error: no gate reads a package leg (require_ci_green.sh grades named REQUIRED_JOBS only), so a red nightly leg is the report. ci_path_gating::continue_on_error_is_a_literal_in_every_workflow guards every workflow; mutation run (an expression back on one step -> red). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0126PDDLB4wNHxKXvWM1VNmu