You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
run/test: diagnostics name the canonical triple, which is the key the reader wrote
`choose_runner` resolves `[target.<triple>].runner` against the canonical
spelling — the output directory's name, and the key every other
`[target.<triple>]` reader uses. The four diagnostics it feeds printed
`tc.targetTriple`, the spelling the driver reported, which on a Linux host is
the same string and on macOS is `arm64-apple-darwin24.6.0`.
Two consequences, both user-facing. The not-found message named a triple the
author never wrote. The unrunnable message printed a `[target.…]` block to
paste whose key no lookup would ever match, so following the advice would have
left the artifact running bare a second time.
`RunnerChoice` now carries `tripleKey`, derived once beside the lookup that
uses it, so the two cannot disagree. The triple is parsed once rather than
three times.
Measured: e2e 330 §3 asserts the message names the triple the manifest key
uses and failed only on macOS ARM64 (run 33609434208).
0 commit comments