Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"Starting watch mode" never finishes & test indicators' state never changes.

See original GitHub issue

Hello,

I’m not sure if I’m the only one experiencing this, but this extension never finishes the “Starting watch mode” phase. Although, all of tests run, but the pass/fail indicator next to the test in the editor never changes from an unfilled green circle to the failed or pass state.

Other than that it’s been working very well.

Thanks for a great extension, it’s been very helpful, I appreciate the time and work that you’ve put into it.

Kindest regards.

Environment

node -v: v8.11.1
npm -v: 6.0.0
npm ls react-scripts (if you haven’t ejected):

@goldberg/nodejs.ts.lib.bare-base@1.0.0 /home/moored/workspaces/au.net.dmdigital.gitlab/goldberg/libraries/bare-base
└── (empty)

Operating system:

$ cat /proc/version
Linux version 4.10.0-38-generic (buildd@lgw01-amd64-059) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #42~16.04.1-Ubuntu SMP Tue Oct 10 16:32:20 UTC 2017

$ lsb_release -a
Distributor ID:	LinuxMint
Description:	Linux Mint 18.3 Sylvia
Release:	18.3
Codename:	sylvia

$ cat /etc/debian_version
stretch/sid

Steps to Reproduce

Clone repo: https://github.com/zeroEvidence/bare-base

$ npm install

Open workspace with vscode v1.22.2, or 1.22.1, or 1.21.1
Disable all extensions except for vscode-jest

Expected Behavior

vscode-jest extension should finish initising watch mode and the test indicators should change state

Actual Behavior

vscode-jest extension “starting watch mode” runs forever.

VSCode developer console log

-1524874876899.log

Issue Analytics

State:
Created 5 years ago
Reactions:55
Comments:28 (5 by maintainers)

Top GitHub Comments

30reactions

connectdotzcommented, Jun 30, 2018

I digged into this a little bit tonight, looks like the hanging watch mode is caused by (facebook/jest#4858), which caused the test results output messaging moved from stdout to stderr for the Runner. Sine vscode-jest (jest-editor-support to be precise) relies on this message on stedout to kick off test result parsing, it therefore hangs indefinitely…

I will submit PRs (both jest-editor-support and vscode-jest) this weekend to address this root cause.

17reactions

crazy4groovycommented, Jun 6, 2018

I’m experiencing this issue with “jest”: “^23.1.0”

Top Results From Across the Web

Run Create-React-App Tests not in Watch Mode

I am looking to add in a precommit hook to run our linter and tests with the pre-commit package. "pre-commit": [ "precommit-msg", "lint",...

vscode-jest - Visual Studio Marketplace

Run all the tests in the workspace upon extension startup, followed by jest watch run for subsequent test/src file changes. Only run tests...

Keep the device awake - Android Developers

The best way to do this is to use the FLAG_KEEP_SCREEN_ON in your activity (and only in an activity, never in a service...

Debug Running Pods | Kubernetes

If your Pod is not yet running, start with Debugging Pods. ... container in Running state, the system tells you when the container...

Exercise Standards for Testing and Training - AHA Journals

Similarly, cycle ergometric exercise tests should start at a low resistance and ... Never use exercise clothing made of rubberized, nonporous material.