Jest // markers at non-test files.

[mhubig]

Hi since the last update of vscode-jest, I randomly find empty jest markers // at non test files.

Im on vscode-jest 2.2.0 / jest 20.0.3 / create-react-app canary ...

[orta]

I've seen this also, off-hand I'm not certain what this is

[mhubig]

They are also shown in test files.

[mhubig]

Disabling InlineErrorMessages by setting "jest.enableInlineErrorMessages": false,
make them disappear.

[tiagor87]

Maybe some regex is doing something wrong. Do you have any public project where this always happens?

[akrigline]

I keep finding these randomly in my files as well. I'll turn off inline Error messages as a temporary fix. Just chiming in to keep this on the radar.

[bookman25]

Do you have a sample repository we can look at to try to reproduce?

[seanpoulter]

Not quite the same cause, but the symptom is the same. If an error stack trace has an incorrect line number when it's transpiled and mapped, you can get some weird results. It happens in our repo. 😞

If anyone's seeing this behavior again, it'd be helpful to include the contents of the Jest Output channel so we can try to determine where the stack trace parsing may be going wrong.