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
Use per-session output directory for Fantom native builds
Summary:
Fixes a race condition where multiple concurrent Jest processes sharing the same checkout could delete each others native binaries. The `globalSetup` in `build.js` previously called `fs.rmSync` on the shared `native-builds/` directory before rebuilding, which could delete binaries that another process workers were actively using (causing `ENOENT` when spawning the fantom-tester binary).
Each Jest session now writes native binaries to `native-builds/<run-id>/`, matching the existing pattern used for JS build outputs (`getTestBuildOutputPath`). The buck isolation directory is shared across sessions so builds remain cached.
Changelog: [Internal]
Reviewed By: christophpurrer
Differential Revision: D101692926
0 commit comments