ci: restore node benchmark contracts #4

Merged
kalmyk merged 1 commit from codex/fix-benchmark-contract-runtime into main 2026-03-26 06:33:50 +00:00
Owner

Summary

  • run perf benchmark contracts with Node+tsx again instead of Bun
  • add an explicit assertion that the 10k range aggregate benchmark stays on the WASM fast path

Why

The failing Forgejo/GitHub CI benchmark was not a new engine slowdown. The perf contract started failing after the benchmark entrypoints were switched to Bun, which caused the range aggregate benchmark to fall back to JS instead of exercising the intended WASM fast path.

Verification

  • pnpm typecheck
  • pnpm bench:smoke
  • BILIG_BENCH_TOLERANCE=1.5 pnpm bench:contracts
## Summary - run perf benchmark contracts with Node+tsx again instead of Bun - add an explicit assertion that the 10k range aggregate benchmark stays on the WASM fast path ## Why The failing Forgejo/GitHub CI benchmark was not a new engine slowdown. The perf contract started failing after the benchmark entrypoints were switched to Bun, which caused the range aggregate benchmark to fall back to JS instead of exercising the intended WASM fast path. ## Verification - pnpm typecheck - pnpm bench:smoke - BILIG_BENCH_TOLERANCE=1.5 pnpm bench:contracts
ci: restore node benchmark contracts
All checks were successful
forgejo-ci / strict-verify (pull_request) Successful in 2m23s
acbe56ef0b
kalmyk merged commit 8702d06689 into main 2026-03-26 06:33:50 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
kalmyk/bilig!4
No description provided.