mirror of
https://github.com/hanzoai/rocm-rs.git
synced 2026-09-30 23:50:28 +00:00
zeekayandHanzo Dev
5626ba6e6a
kv named the wrong server binary (kv-server, not valkey-server) and assumed a C compiler the reusable installs only for Go callers; forum assumed a ruby the reusable never provisions; rocm-rs left gpu-sort on, whose nested nightly build-std step no stock runner can do; insights-rs asked for --all-features, which selects the live-endpoint e2e feature. Co-authored-by: Hanzo Dev <[email protected]>
20 lines
997 B
YAML
20 lines
997 B
YAML
# Rust bindings to the ROCm stack (HIP, rocBLAS, rocFFT, MIOpen, …).
|
|
#
|
|
# Gate: the crate compiles against the bindings committed under src/*/bindings.rs.
|
|
# SKIP_BINDGEN is the escape build.rs itself declares for exactly this case — a
|
|
# host with no /opt/rocm regenerates nothing and uses the checked-in bindings, so
|
|
# what CI proves is that the Rust in this repo compiles against the bindings this
|
|
# repo ships. Regenerating them needs ROCm headers and an AMD host; that is a
|
|
# hardware lane, not a push gate.
|
|
#
|
|
# Features are the default set minus `gpu-sort`, which Cargo.toml documents as
|
|
# the one to turn off where "the kernel's nested nightly+build-std cargo build is
|
|
# unavailable" — a stock runner is precisely that host. Leaving it on would make
|
|
# this gate report on the absence of a nightly amdgcn toolchain rather than on
|
|
# the code.
|
|
test:
|
|
- name: build
|
|
run: |
|
|
set -euo pipefail
|
|
SKIP_BINDGEN=1 cargo build --locked --no-default-features --features macros,miopen
|