TypeError when testcafe is stopping about testcafe-live HOT 10 CLOSED

mine also stopped TCP? error.

TestCafe Live watches the files and reruns
the tests once you've saved your changes.

You can use the following keys in the terminal:
'ctrl+s' - stop current test run;
'ctrl+r' - restart current test run;
'ctrl+w' - turn off/on watching;
'ctrl+c' - close browsers and terminate the process.


Test run is starting...
 Running tests in:
 - Chrome 66.0.3359 / Mac OS X 10.13.2

 Getting Started

Stopping TestCafe Live...
events.js:167
      throw er; // Unhandled 'error' event
      ^

Error: read ECONNRESET
    at TCP.onread (net.js:659:25)
Emitted 'error' event at:
    at Socket.onerror (_stream_readable.js:696:12)
    at Socket.emit (events.js:182:13)
    at Socket.EventEmitter.emit (domain.js:442:20)
    at emitErrorNT (internal/streams/destroy.js:92:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
    at process._tickCallback (internal/process/next_tick.js:174:19)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

from testcafe-live.

Hi @shinriyo @Klaster1 @myxious @amilajack @ltran273 @vickvasquez @oshoham @MoritzR the issue with ECONNRESET must be fixed in [email protected], could you please try it on your machines?

from testcafe-live.

@AndreyBelym I couldn't reproduce the issue anymore, looks like the fix works. Great work!

from testcafe-live.

@AndreyBelym Did a few runs on node 10.1.0 with both testcafe v0.21.1 and v0.22.0 and could confirm that it seems to be fixed with v0.22.0, thanks!

from testcafe-live.

Hi @TauPan, I need some time to reproduce the problem. I guess that concurrency or quarantine mode can cause the failure, could you please try to run tests without enabling these features?

from testcafe-live.

Hi, I'm trying to run it without concurrency or quarantine... I just noticed I gave the wrong browser above. I'm usually running with chromium:headless. Might that be relevant as well?

from testcafe-live.

Can't reproduce it without concurrency and quarantine with graphical OR headless chromium.

from testcafe-live.

I get the same error when running testcafe and testcafe-live with Node 10, but if I use Node 9 binary, everything works fine or at least stable enough.

from testcafe-live.

@Klaster1 @shinriyo may be tracked in DevExpress/testcafe#2711

from testcafe-live.

I can't reproduce the issue with Live mode integrated into [email protected]: TestCafe 1.0.0 Released: Live mode. If you still can reproduce with [email protected], please create a new bug report in the main TestCafe repository.

from testcafe-live.