Rust adapter: selective runs on real repositories

Aberta
#131 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
30/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
github-actions, rust
Domínio
build-system, ci-cd

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
TypeScript
Estrelas
0
Forks
4
Merge médio
18h 41min
PRs com merge (30d)
48

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de DiffCI/core

Todas as issues de DiffCI/core

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.