Jest: "Test run was interrupted." happens with npm run test

Is this a bug report?

Yes

Can you also reproduce the problem with npm 4.x?

Yes

Which terms did you search for in User Guide?

Environment

1. node -v: 6.9.1
2. npm -v: 4.6.1
3. npm ls react-scripts (if you haven’t ejected): 1

Then, specify:

1. Operating system: Windows 8.1

Steps to Reproduce

(Write your steps here:)

1. npm run test

Expected Behavior

Unit tests would execute

Actual Behavior

Consistently get:

“Test run was interrupted.”

Reproducible Demo

Tough to come up with a case. I did notice that adding --runInBand seems to work fine (though slower).

I’m thinking this is due to my Anti Virus, and is likely an issue with Jest, however, since everyone here works with similar configurations, I figured I’d start here before posting over there.

Unfortunately, I can’t prove out my AV theory, as I need my IT team to allow me to stop it.

[ArmorDarks]

Yeap, worth a try.

I’m not sure that I will be able to provide good track down of issue, though, since issue seems to be sporadic and happens only sometimes, and that “sometimes” usually starts to happen only after Jest works for a while and some good amount of watch events happens.

[markguckian]

Looks like Cmder/ConEmu is triggering an [Enter] key somehow which is setting the ‘interrupted’ state in testWatcher to true.

(jest-cli/build/watch.js)

(jest-cli/build/constants.js)

(Using react-scripts 1.0.7)