Skip to content

fix: Correctly parse bencher thresholds - #655

Merged
samuelburnham merged 1 commit into
mainfrom
fix/bencher-thresholds-split
Oct 1, 2026
Merged

samuelburnham merged 1 commit into
mainfrom
fix/bencher-thresholds-split

Conversation

@samuelburnham

Copy link
Copy Markdown
Member

The thresholds input spans several lines, one per measure. Replacing the unquoted array expansion with read -a kept only the first line, so every measure after the first lost its flags and the first lost its boundaries; bencher rejected the model with "no boundary provided" and Benchmark main failed at the tracking step.

read -d '' consumes the input to its end and still splits on all whitespace, reproducing the original token list without globbing. It reports end of input as a failure, hence the trailing || true.

Fixes https://github.com/argumentcomputer/ix/actions/runs/36905045151

The `thresholds` input spans several lines, one per measure. Replacing
the unquoted array expansion with `read -a` kept only the first line,
so every measure after the first lost its flags and the first lost its
boundaries; bencher rejected the model with "no boundary provided" and
Benchmark main failed at the tracking step.

`read -d ''` consumes the input to its end and still splits on all
whitespace, reproducing the original token list without globbing. It
reports end of input as a failure, hence the trailing `|| true`.
@samuelburnham
samuelburnham added this pull request to the merge queue Oct 1, 2026
Merged via the queue into main with commit 56f4a84 Oct 1, 2026
14 checks passed
@samuelburnham
samuelburnham deleted the fix/bencher-thresholds-split branch October 1, 2026 22:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants