Rust adapter: selective runs on real repositories

Offen
#131 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
30/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
github-actions, rust
Bereich
build-system, ci-cd

Rechercherichtung

Start with the Cargo adapter registration and the rust-lang/glob replay pinned in #95, and read #91's out-of-workspace manifest agreement plus #92–#95 for the adapter contract. Compare how existing adapters classify non-code paths and runtime-input tokens, then use those paths as the reference. Done means at least one historical revision in the pinned replay narrows instead of staying FULL, while the selected tests still catch the same failures as the full baseline.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Follow-up to #62. Once #92–#95 merge, the Rust (Cargo) adapter is registered and safe, but it cannot narrow a real repository yet: the pinned rust-lang/glob replay stayed FULL on every revision. This issue tracks the work needed for real-repository selectivity.

Scope

  • External dependency inputs. The blockers for non-workspace packages, dependency features or default-features = false, build scripts and proc macros currently run over every resolved package. Apply them only to the crates a change reaches, wherever the dependency graph can show that.
  • Runtime-input tokens. fs, unsafe, exists, metadata, process and similar words in a source file force a repo-wide full run. Narrow this to the owning crate and its dependents.
  • Out-of-workspace Cargo.toml. As agreed in #91: treat unmodeled manifests as ownership boundaries and require full validation only when the changed set or its dependents reach them. Keep the repo-wide fallback when metadata can't tell.
  • CI invocation evidence. Accept common toolchain setup and cache steps (for example dtolnay/rust-toolchain, Swatinem/rust-cache) when they don't change how cargo test runs.
  • Non-code paths. Classify README.md, docs/** and similar files the way the other adapters do, instead of forcing a full run.
  • Workspace scope. Handle default-members and a root [package], where plain cargo test covers only some members.

Done when a pinned public Rust replay narrows at least one historical revision, and the selected tests catch the same failures as the full baseline.

Maintainer: @FredApps.

Vorherrschende Sprache
TypeScript
Sterne
0
Forks
4
Ø Merge
18 Std. 41 Min.
Gemergte PRs (30 T.)
48

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus DiffCI/core

Alle Issues in DiffCI/core

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.