ReviewOS

home-lang/home

Port Bun.Glob concurrent scan and match stress corpus

#126
Closed chris opened this 9 days ago ·
9 days ago

Scope

Activate the byte-identical js/bun/glob/stress.test.ts corpus as the next focused placeholder removal.

The two upstream tests exercise:

  • 1,000 concurrent Glob.scan operations after fixture setup
  • 10,000 repeated Glob.match operations

This builds on the already passing Bun.Glob match, path-length, and 160-case scan corpus coverage.

Baseline

The exact file is currently rewritten to one native todo:

  • 0 pass
  • 0 fail
  • 0 unsupported
  • 1 todo

The local file is byte-identical to ~/Code/bun.

Acceptance

  • Keep the upstream corpus byte-identical.
  • Run both original stress tests as real tests with no native todo.
  • Provide the original fixture graph through the Home runtime bridge.
  • Add a permanent unchanged-corpus regression.
  • Preserve existing Bun.Glob corpus results.
  • Pass the exact file and full home_test gate.
  • Commit and push as Chris Breuer with no coauthors.
  • Link completion to #66.
9 days ago

Implemented and pushed in 3e13ec9.

The byte-identical upstream stress file now runs both original tests through the native linked Bun.Glob path. The bridge lowers only the fixture helper import and recreates the original twelve-file graph under a platform-specific node:os tmpdir root, preventing virtual fixture setup from shadowing repository paths.

Validation:

  • exact stress.test.ts: 2 pass, 0 fail, 0 todo, 0 unsupported
  • exact scan→stress→scan sequence: 160 pass, 2 pass, 160 pass
  • workspace shadow path is not recreated
  • permanent unchanged-corpus regression preserves Array(1000) concurrent scans and 10,000 matches
  • upstream file remains byte-identical
  • Zig formatting and diff checks pass
  • full home_test gate passes with no failures

The cross-file shadow interaction found during integration was corrected before publication. The commit is authored and committed as Chris Breuer with no coauthors. This advances #66.

Sign in to comment on this issue.