Skip to content

Dogfood CARGO_REGISTRIES_CRATES_IO_PROTOCOL=sparse in CI #107342

Closed

Description

@jyn514

Sparse-registry was recently stabilized and cargo itself has started dogfooding it in CI: rust-lang/cargo#11632. We should do the same in rust-lang/rust, both to speed up CI and to test out the feature.

I think around

rust/src/ci/run.sh

Lines 129 to 130 in beefcf8

export COMPILETEST_NEEDS_ALL_LLVM_COMPONENTS=1
is the right place to set this; we should verify by inspection that the feature is being used in CI before merging.

Activity

  1. added
    T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.
    T-cargoRelevant to the cargo team, which will review and decide on the PR/issue.
    T-crates-ioRelevant to the crates.io team, which will review and decide on the PR/issue.
    on Jan 27, 2023
  2. added a commit that references this issue on Feb 3, 2023
    5d32458
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

T-cargoRelevant to the cargo team, which will review and decide on the PR/issue.T-crates-ioRelevant to the crates.io team, which will review and decide on the PR/issue.T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions