The official source reports this update: nightly-last-green: Add klxpu (KUNLUNXIN XPU) self-hosted CI for the v1 unit suite (#8923). Run the tests/unit/v1 suite on a self-hosted KUNLUNXIN XPU runner inside the vendor container, one test file per subprocess (torch_xmlir inits CUDA at import, so pytest --forked is unusable). A blocklist keeps new tests running by default: ignore.txt whole files/dirs that hang or wholly fail deselect.txt individual node ids that fail Environment handling, all per-machine via Actions variables so the same workflow works on hosts with different networks and storage: proxy (KLXPU_HTTP_PROXY/KLXPU_HTTPS_PROXY): unset means direct access.
Canonical AI event
Nightly adds self-hosted CI for v1 unit tests on KUNLUNXIN XPU
The v1 unit suite now runs on a self-hosted KUNLUNXIN XPU runner.
30 Oct 20261 verified claims1 sources3 observations
This official update documents a development concerning nightly-last-green: Add klxpu (KUNLUNXIN XPU) self-hosted CI for the v1 unit suite (#8923). Its practical significance depends on the scope and evidence stated by the source.
Read the official source update and verify its stated scope, evidence and timing before acting on it.
Connected knowledge
Entities affected by this event
Continue this topic
Related verified updates
Evidence trail
Sources behind the event
Microsoft DeepSpeed official releasesnightly-last-green: Add klxpu (KUNLUNXIN XPU) self-hosted CI for the v1 unit suite (#8923)Microsoft DeepSpeed official releasesnightly-last-green: Add KLXPU (KUNLUNXIN XPU) accelerator (#8799)Microsoft DeepSpeed official releasesnightly-last-green: Add vocabulary-parallel logprobs, entropy and KL ops (#8791)
Editorial presentation
Open story