Skip to content

Move the remaining scripts/ tooling to Rust (cargo xtask / e2e scenarios) #572

Open

Description

@rominf

cargo xtask already owns packaging, signing, coverage and the install-lifecycle harness (#139). About 9.5k lines of Python and shell tooling remain under scripts/ and tests/remote-ssh/. All of it already needs the Rust toolchain, because it builds or drives the rocm binary. Porting it would:

  • keep its checks next to the Rust code they validate, such as expectations.toml parsing, asset naming and signing;
  • bring them under cargo test and the per-crate coverage floors;
  • drop Python from the required CI jobs.

Proposed order, one PR each:

Staying native:

  • install.sh / install.ps1, which run before any Rust binary exists
  • docs/rocm-docs/conf.py
  • .github/scripts/Invoke-WslBash.ps1
  • setup-wsl-portable-build-deps.sh

Each port keeps its checks assertion for assertion, and its --self-test becomes cargo test coverage.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions