docs(vllm): record tsingmicro tsm260610 0.20.2 F/T E2E result (#872)
- docs(vllm): record tsingmicro tsm260610 0.20.2 F/T E2E result
The TX8110 backend passes the 0.20.2 dual-compiler end-to-end run: both the FlagTree and the vendor Triton path serve Qwen3-4B and return byte-identical outputs for the anchor prompts, with the same operator routing on both paths.
Records the three TX8110-specific pitfalls fixed along the way (paged KV cache writes need base indexing, 0-dim .item() faults, strided device reads are ~80x slower than contiguous), plus the dispatch configuration that routes attention to the vendor backend and rms_norm / rotary_embedding to reference.
Only the runtime side was exercised, so the per-backend facility booleans (deps_app / launch_docs / image_tag) stay unset.
This PR was written in part with the assistance of generative AI.
- docs(vllm): link the tsingmicro 0.20.2 enablement PR
The verified wheel was built from the PR head, so the backend record and the matrix track it.
This PR was written in part with the assistance of generative AI.
Co-authored-by: flagos-ci noreply@flagos.net
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802047560号
build-infra
FlagOS container image build infrastructure. This repo defines and builds the base images — a vendor’s SDK and toolchain on an OS base — that FlagOS runtime images are built on.
📖 Documentation: https://flagos-ai.github.io/release-info/
The docs (supported backends, per-image environment, dependencies) are generated from
configs.yaml+base/, so they can’t drift from the source.Layout
configs.yamlbase/<vendor>-<backend>scripts/build_base.pyscripts/generate_matrix.pyconfigs.yamlscripts/build_runtime.py.github/build-config.ymlruntime/packaging/flagtree/docs/Quick start
Build a base image locally:
In CI, base images are built on demand via the Base Image Build (manual) workflow (
workflow_dispatch) — pick a backend (orall) and whether to push.To add a vendor/backend, see the onboarding guide.