Rust adapter: selective runs on real repositories

未关闭
#131 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
30/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
github-actions, rust

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
TypeScript
星标
0
派生
4
平均合并
18 小时 41 分钟
30 天内合并 PR
48

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

DiffCI/core 的其他 Issue

查看 DiffCI/core 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。