Repository navigation
preflight: mlx-metal-0-40-2 and metal-0-40-2 admit the v0.40.3 lineage - #491
Conversation
The v0.40.3 fold (#488) is Go only: MLX a59cc231 and llama.cpp b11351 stay, so its builds share the v0.40.2 payload and these profiles (ADR 0032), as rocm7-0-40-2 already admits it. The fold's head, 0.40.2-dynres.1-6-g9f3baaf, passed both on Metal (PASS=23 SKIP=16 and PASS=6 SKIP=12). 0.40.4 stays refused. Both profiles' tests admit a 0.40.3-dynres stamp and reject 0.40.4; test_verdicts 259 OK. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
gfx1151 review at
Merging at this head under the maintainer's standing permission. From |
|
CUDA review at #492 widens the CUDA pair to the identical pattern, so all five 0.40.2 profiles stay in step: rocm7 (#488), the two Metal profiles (this PR) and the two CUDA profiles (#492). The two PRs touch different profile blocks and different test classes, so they merge in either order. From |
Both Metal profiles now admit the v0.40.3 lineage, as
rocm7-0-40-2does since #488. Preflight expectations only.a59cc231and llama.cpp b11351 (631109b34) don't move, so its builds share the v0.40.2 payload (ADR 0032).0.40.2-dynres.1-6-g9f3baaf, passed both profiles on Metal:mlx-metal-0-40-2PASS=23 SKIP=16 andmetal-0-40-2PASS=6 SKIP=12 (fold: upstream v0.40.3 — the local GGUF compatibility migration pauses #488, 6148015236).^0\.40\.[23]-dynres(\.\d+)?-\d+-g[0-9a-f]{7,40}$. 0.40.4 stays refused, because its rc1 moves llama.cpp to b11521.test_verdictsrows admit0.40.3-dynres-0-gabcdef0and reject0.40.4-dynres-0-gabcdef0. The MLX row also admits the fold head's own stamp.test_verdicts.py: 259 tests OK.The CUDA host widens
cuda-0-40-2andmlx-cuda-0-40-2in its own PR. This one touches only the Metal profiles, so the two PRs don't conflict.macbook-pro-m5-max-128GB/mlx-metal🤖 Generated with Claude Code