fix: correct check for compatible find binary

[SimenB]

Summary

Fixes #10339

Test plan

Verified on Windows VM. Not sure how to write a test for this… I'm quite confused by why our windows tests pass without this - I doubt watchman is installed. Maybe they have some other find?

[SimenB]

FYI @richardlau 🙂

[richardlau]

Verified on Windows VM. Not sure how to write a test for this… I'm quite confused by why our windows tests pass without this - I doubt watchman is installed. Maybe they have some other find?

The test mocks child_process so doesn't actually spawn.
https://github.com/facebook/jest/blob/41436be27aef1b5968d5360062e5599d206f16d8/packages/jest-haste-map/src/crawlers/__tests__/node.test.js#L11-L35

[SimenB]

Verified on Windows VM. Not sure how to write a test for this… I'm quite confused by why our windows tests pass without this - I doubt watchman is installed. Maybe they have some other find?

The test mocks child_process so doesn't actually spawn.

Right, but we test Jest using Jest itself, and spawn an instance of Jest in every e2e test. So I'd have thought CI would fail when trying to run any tests, not these specific unit tests.

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.