Successful tests are marked as failed because of DISCONNECTED
See original GitHub issueChrome 51.0.2704 (Windows 10 0.0.0): Executed 21 of 21 DISCONNECTED (14.456 secs / 4.149 secs)
Firefox 47.0.0 (Windows 10 0.0.0): Executed 21 of 21 DISCONNECTED (14.419 secs / 4.128 secs)
Safari 9.0.0 (Mac OS X 10.11.0): Executed 21 of 21 SUCCESS (4.996 secs / 4.118 secs)
Safari 8.0.8 (Mac OS X 10.10.5): Executed 21 of 21 SUCCESS (4.349 secs / 4.079 secs)
Edge 13.10586.0 (Windows 10 0.0.0): Executed 21 of 21 DISCONNECTED (14.333 secs / 4.073 secs)
IE 11.0.0 (Windows 8.1 0.0.0): Executed 21 of 21 DISCONNECTED (14.91 secs / 4.05 secs)
IE 10.0.0 (Windows 8 0.0.0): Executed 21 of 21 SUCCESS (4.308 secs / 4.051 secs)
IE 9.0.0 (Windows 7 0.0.0): Executed 21 of 21 SUCCESS (4.286 secs / 4.029 secs)
Mobile Safari 7.0.0 (iOS 7.1.0): Executed 21 of 21 SUCCESS (4.312 secs / 4.051 secs)
While running the tests, I often see something like this:
15 07 2016 10:26:30.397:WARN [IE 10.0.0 (Windows 8 0.0.0)]: Disconnected (1 times), because no message in 10000 ms.
IE 10.0.0 (Windows 8 0.0.0) ERROR
Disconnected, because no message in 10000 ms.
15 07 2016 10:26:30.397:INFO [karma]: Restarting IE 10.0.0 (Windows 8 0.0.0) (1 of 3 attempts)
But IE tests has already passed before this message.
Let me know how I can provide more information.
This is my dependencies:
βββ babel-cli@6.10.1
βββ babel-core@6.10.4
βββ babel-eslint@6.1.0
βββ babel-loader@6.2.4
βββ babel-plugin-__coverage__@11.0.0
βββ babel-preset-es2015@6.9.0
βββ babel-preset-es2015-loose@7.0.0
βββ babel-preset-react@6.11.1
βββ browser-sync@2.13.0
βββ classnames@2.2.5
βββ element-resize-detector@1.1.5
βββ eslint@2.13.1
βββ eslint-config-rackt@1.1.1
βββ eslint-plugin-react@5.2.2
βββ gulp@3.9.1
βββ gulp-debug@2.1.2
βββ gulp-watch@4.3.8
βββ invariant@2.2.1
βββ istanbul-combine@0.3.0
βββ jasmine-core@2.4.1
βββ karma@1.1.1
βββ karma-babel-preprocessor@6.0.1
βββ karma-chrome-launcher@1.0.1
βββ karma-coverage@1.1.0
βββ karma-jasmine@1.0.2
βββ karma-sauce-launcher@1.0.0
βββ karma-sourcemap-loader@0.3.7
βββ karma-spec-reporter@0.0.26
βββ karma-webpack@1.7.0
βββ lodash@4.13.1
βββ onchange@2.5.0
βββ react@15.1.0
βββ react-dom@15.1.0
βββ rimraf@2.5.2
βββ tslint@3.13.0
βββ typescript@1.8.10
βββ typings@1.3.1
βββ webpack@1.13.1
βββ yargs@4.8.0
Issue Analytics
- State:
- Created 7 years ago
- Reactions:7
- Comments:7
Top Results From Across the Web
Long running unit test marked as passed fails TFS build
I have a few long running unit tests (10+ minutes). The unit tests can be run successfully locally on developer's machine inside VS2017....
Read more >karma spec failures - Chrome ERROR: Disconnected ... - GitLab
An error occurred while fetching the assigned iteration of the selected issue.
Read more >Error Messages During Test Execution - LambdaTest
This happens due to Username or Access Key passed by you is missing or invalid. How To Resolve?β. Go to LambdaTest Automation Dashboard....
Read more >Lifecycle - Application Migration Service - AWS Documentation
Ready for testing - The server has been successfully added to Application Migration ... The step on which Initial Sync failed will be...
Read more >Troubleshooting App Connectors - Zscaler Help
Troubleshooting App Connectors Β· App Connector Not Connected to the Cloud Β· DNS Failure, But App Connector Successful Β· SSL Interceptions Β· Memory...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
So after a few days of messing around, Iβve come to realize that various browsers will fail to stop if you use any form of code coverage.
isparta-loader
,babel-plugin-istanbul
, etc. all cause Edge 14, Safari 9, and Safari 8 to hang on Sauce Labs.This error is still happening even though Iβve removed my code coverage tools. My errors look like this:
With
concurrency: 1
, tests in Chrome 55 pass, then Chrome 56 starts, and then Chrome 55 returns an error due to disconnecting. Similarly, Chrome 54 has a disconnect error after its tests pass and Chrome 55 starts, and Chrome 56 passes with no disconnect error. Chrome 55 should disconnect after it passes, right? Why is this an error?Iβm testing Chrome 54-56. When I set
concurrency: 5
, only Chrome 56 fails due to disconnection. Odd behavior.Does anyone know other solutions?