Closed kubal5003 closed 6 years ago
Wallaby was working fine for my project, but then something happened
This means that the issue is likely your project specific, I suspect some of the modules you have started to use lately may be causing it. Having said that, we are happy to help troubleshooting the issue and to help configure wallaby correctly for your case.
Ideally we'll need a sample project where we can reproduce the issue, but we understand that it may be hard to create. So let's try to isolate it first.
Please try this:
emitModulePaths
webpack config property, and when the Cannot find module ...
error shows up, it should now display the module name instead of a number. Please share the module name.
var webpackPostprocessor = wallabyWebpack({
...
set wallaby workers count to 1 (to make the issue causing spec finding easier)
module.exports = function (wallaby) {
...
return {
...
tests
setting and comment out all specs
tests: [
// {pattern: 'src/**/*spec.ts', load: false}
],
tests
to see if the tests pass,Once you find the spec that is causing the issue, check what modules are imported by it (and by modules that the spec imports). It's likely something that you started to use recently.
Also please do this:
Share the test-config/spec-bundle-wallaby.js
file and your package.json
's file dependencies
and devDependencies
sections.
Edit your wallaby config to output more debugging info:
module.exports = function (wallaby) {
...
return {
...
debug: true }; };
and when the error shows up, search the Wallaby Console output for `wallaby:project File cache`, open the folder, archive the `instrumented/____wallaby-bundle.js` file in there and send it to us to hello@wallabyjs.com.
Could you also please
workers: {initial: 1, regular: 1}
setting) to see if it helps.Hi, sorry for late reply as I was travelling yesterday. First of all thank you for helping with tracing the problem.
I did add the emitModulePaths
(nice! thank you!) and it seems that the module that breaks is the node_modules/@angular/core/esm5/testing.js which has all the basic infrastructure of Angular 5 testing utilities.
That means that if my tests are to blame this seems like a derived error and not the real source of the problem. The path to the file that is reported is correct and the file exists on disk.
Chrome version installed: 64.0.3282.140 (I am guessing that wallaby is using whatever is installed? if not please tell me where to look )
Workers - set to 1, 1 as suggested. With excluding the tests and adding them gradually - I will try, however this might not be totally easy since we now have ~1200 tests in 228 spec files.
test-config/spec-bundle-wallaby.js
Error.stackTraceLimit = Infinity;
require('core-js/es6');
require('core-js/es7/reflect');
require('./matchers');
require('zone.js/dist/zone');
require('zone.js/dist/long-stack-trace-zone');
require('zone.js/dist/proxy'); // since zone.js 0.6.15
require('zone.js/dist/sync-test');
require('zone.js/dist/jasmine-patch'); // put here since zone.js 0.6.14
require('zone.js/dist/async-test');
require('zone.js/dist/fake-async-test');
/**
* RxJS
*/
require('rxjs/Rx');
var testing = require('@angular/core/testing');
var browser = require('@angular/platform-browser-dynamic/testing');
testing.TestBed.initTestEnvironment(
browser.BrowserDynamicTestingModule,
browser.platformBrowserDynamicTesting()
);
package.json dependencies:
"@angular/common": "^5.2.0",
"@angular/core": "^5.2.0",
"@angular/platform-browser": "^5.2.0",
"@angular/platform-browser-dynamic": "^5.2.0",
"@angular/router": "^5.2.0",
"@ng-idle/core": "^2.0.0-beta.13",
"@ngx-translate/core": "^9.1.0",
"@ngx-translate/http-loader": "^2.0.1",
"core-js": "^2.5.1",
"dexie": "^2.0.1",
"http-proxy-middleware": "^0.17.4",
"lodash": "^4.17.4",
"moment": "^2.18.1",
"rxjs": "^5.5.6",
"typescript-memoize": "0.0.4",
"zone.js": "^0.8.20"
package.json dev dependencies:
"@angular/compiler": "^5.2.0",
"@angular/compiler-cli": "^5.2.0",
"@ngtools/webpack": "^1.9.4",
"@types/express": "^4.0.39",
"@types/ip": "~0.0.29",
"@types/jasmine": "^2.8.4",
"@types/lodash": "^4.14.92",
"@types/mongodb": "^3.0.1",
"@types/node": "^9.3.0",
"@types/selenium-webdriver": "^3.0.8",
"angular-router-loader": "~0.8.2",
"angular2-template-loader": "~0.6.2",
"awesome-typescript-loader": "~3.4.1",
"babel-polyfill": "^6.26.0",
"codelyzer": "^4.0.2",
"compression": "^1.7.1",
"config": "^1.28.1",
"copy-webpack-plugin": "^4.2.3",
"css-loader": "~0.28.0",
"es6-promise": "~4.1.0",
"es6-promise-loader": "~1.0.2",
"express": "^4.16.2",
"express-handlebars": "latest",
"extract-text-webpack-plugin": "^3.0.2",
"file-loader": "^1.1.5",
"html-loader": "^0.5.1",
"html-webpack-plugin": "~2.30.1",
"htmllint-cli": "0.0.6",
"image-webpack-loader": "3.4.2",
"imports-loader": "~0.7.1",
"inquirer-directory": "^2.1.0",
"ip": "~1.1.5",
"istanbul-instrumenter-loader": "~3.0.0",
"jasmine-spec-reporter": "^4.1.1",
"js-sha256": "^0.7.1",
"json-loader": "~0.5.4",
"karma": "~2.0.0",
"karma-chrome-launcher": "~2.2.0",
"karma-coverage": "~1.1.1",
"karma-jasmine": "^1.1.1",
"karma-junit-reporter": "^1.2.0",
"karma-mocha-reporter": "^2.2.5",
"karma-phantomjs-launcher": "~1.0.4",
"karma-remap-coverage": "0.1.4",
"karma-sourcemap-loader": "~0.3.7",
"karma-webpack": "^2.0.9",
"memory-cache": "^0.2.0",
"mongodb": "^3.0.1",
"node-sass": "^4.7.2",
"npm-run-all": "^4.1.2",
"plop": "^1.9.0",
"protractor": "~5.2.0",
"protractor-image-comparison": "^1.4.0",
"raw-loader": "^0.5.1",
"request-promise": "^4.2.2",
"rimraf": "~2.6.1",
"run-middleware": "^0.6.6",
"sass-lint": "^1.12.1",
"sass-loader": "^6.0.5",
"source-map-loader": "^0.2.3",
"string-replace-loader": "~1.3.0",
"style-loader": "^0.19.0",
"to-string-loader": "~1.1.5",
"ts-node": "~3.3.0",
"tslint": "~5.8.0",
"tslint-loader": "~3.5.2",
"typescript": "2.6.2",
"wallaby-webpack": "^3.9.4",
"webpack": "~3.8.1",
"webpack-bundle-analyzer": "^2.9.2",
"webpack-dev-middleware": "^2.0.4",
"webpack-dev-server": "^2.11.0",
"webpack-hot-middleware": "^2.21.0",
"webpack-md5-hash": "^0.0.6"
Recently we did not start using any new libraries (at least not that I'm aware of..) - last thing we did was I guess upgrade to Angular 5.2.0, but after that wallaby was working fine for a longer period as far as I recall.
Thanks for providing the details!
workers: {initial: 1, regular: 1}
setting?workers: {initial: 1, regular: 1}
setting) to see if it helps.I did trace the 'export is undefined problem' - the path that is shown is always referring to the currently modified spec file. I will continue to investigate (including Electron runner, send the bundle as requested etc.)
From time to time I'm getting:
One more interesting thing: wallaby:workers [4nwb9] Sandbox is responsive, closing it
I suddenly experienced the same problem with my Angular hybrid application: "angular": "1.6.9", "@angular/core": "5.2.5", "wallaby-webpack": "3.9.4", "webpack": "3.11.0", env: chrome
Uncaught Error: Cannot find module '.\wallaby-bundle.js' (.\wallaby-bundle.js) Uncaught Error: Cannot find module '272' (C:\Data\ari2\ari-ui-web-content\node_modules\@angular\core\esm5\testing.js)
Setting workers: {initial: 1, regular: 1} does work for me when starting WallabyJS en writing code.
I noticed that when I get the error, and then change some code (comment), the error goes away. When I restart WallabyJS, the errors are back
Ok, so it is an issue with headless Chrome, when running large (bundle) files in parallel. That is why we couldn't reproduce it before and that is why the issue only showed up for some user, the bundle size needs to be >=~7mb, and we were trying smaller projects.
I'm merging the following issues into this one (@Conrad777 and @jkyoutsey, please subscribe to this issue to get updates): https://github.com/wallabyjs/public/issues/1507 https://github.com/wallabyjs/public/issues/1515
We'll be creating a small sample to submit to Chrome team, so that they could investigate and fix the issue.
For those who are encountering the issue and for those who'll encounter it before it is fixed, there are 3 confirmed workarounds.
module.exports = function (wallaby) {
...
return {
...
--headless
flag passed by Wallaby to Chrome by default and your tests should pass. However Chrome instance will be visible on your screen. env: {
kind: 'chrome',
+ params: { runner: ' '}
},
Looks like we have found a flag in Chrome that can fix the issue in headless mode.
@kubal5003 @Conrad777 @aikrez @jkyoutsey please try updating to the latest core v1.0.550, removing any workaround settings (if you have set any), and try running wallaby.
I can confirm that there no more errors with v1.0.550 without workarround setting. Thanks!
Awesome, thanks for the update!
I updated to latest core (Wallaby.js core v1.0.550 has been successfully installed) and still have the same issue. With multiple workers I get this:
0 failing tests, 0 passing
Uncaught Error: Cannot find module './src/main/ui/wallabyTest.js' (./src/main/ui/wallabyTest.js)
at http://localhost:62281/wallaby-webpack.js?1518794237667:1
Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
at http://localhost:62281/wallaby-webpack.js?1518794237667:1
It appears that it doesn't want to run any tests now. Get errors in the console too:
[Info] Fri, 16 Feb 2018 16:55:29 GMT wallaby:project Wallaby config: /Users/me/src/myapp/branches/me-70824-httpclient/wallaby.js
[Info] Started Wallaby.js Core v1.0.550
[Info] Fri, 16 Feb 2018 16:55:29 GMT wallaby:fs File added: src/main/ui/index.html
...
[Info] Fri, 16 Feb 2018 16:55:30 GMT wallaby:project File cache: /Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f
[Info] Fri, 16 Feb 2018 16:55:30 GMT wallaby:uiService Listening port 51235
[Info] Fri, 16 Feb 2018 16:55:31 GMT wallaby:workers Parallelism for initial run: 6, for regular run: 3
[Info] Fri, 16 Feb 2018 16:55:31 GMT wallaby:workers Starting run worker instance #0
[Info] Fri, 16 Feb 2018 16:55:31 GMT wallaby:workers Starting run worker instance #1
[Info] Fri, 16 Feb 2018 16:55:31 GMT wallaby:workers Starting run worker instance #2
[Info] Fri, 16 Feb 2018 16:55:31 GMT wallaby:workers Starting run worker instance #3
[Info] Fri, 16 Feb 2018 16:55:31 GMT wallaby:workers Starting run worker instance #4
[Info] Fri, 16 Feb 2018 16:55:31 GMT wallaby:workers Starting run worker instance #5
[Info] Fri, 16 Feb 2018 16:55:31 GMT wallaby:workers Web server is listening at 50646
[Info] Fri, 16 Feb 2018 16:55:31 GMT wallaby:workers Started run worker instance (immediate) #0
[Info] Fri, 16 Feb 2018 16:55:31 GMT wallaby:workers Started run worker instance (immediate) #1
[Info] Fri, 16 Feb 2018 16:55:31 GMT wallaby:workers Started run worker instance (immediate) #2
[Info] Fri, 16 Feb 2018 16:55:31 GMT wallaby:workers Started run worker instance (immediate) #3
[Info] Fri, 16 Feb 2018 16:55:31 GMT wallaby:workers Started run worker instance (immediate) #4
[Info] Fri, 16 Feb 2018 16:55:31 GMT wallaby:workers Started run worker instance (immediate) #5
...
[Info] Fri, 16 Feb 2018 16:55:52 GMT wallaby:postprocessor New compiler created
[Info] Fri, 16 Feb 2018 16:55:52 GMT wallaby:postprocessor Webpack compilation started
[Info] Fri, 16 Feb 2018 16:56:03 GMT wallaby:postprocessor Webpack compilation finished
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:postprocessor Emitting 2160 files
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:project Postprocessor execution finished
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:project Test run started; run priority: 3
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:project Running all tests
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:workers Starting test run, priority: 3
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:workers Distributing tests between 6 workers
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:workers Running tests in parallel
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Starting sandbox [worker #0, session #puape]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Starting sandbox [worker #1, session #dhqtn]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Starting sandbox [worker #2, session #2fhfu]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Starting sandbox [worker #3, session #vvrn2]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Starting sandbox [worker #4, session #s1f83]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Starting sandbox [worker #5, session #o48zp]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Preparing sandbox [worker #0, session #puape]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:browserRunner Total files to load in sandbox: 28
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:browserRunner Sandbox is generated [worker #0, session #puape]: http://localhost:50646/wallaby_sandbox0.html
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Preparing sandbox [worker #1, session #dhqtn]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:browserRunner Total files to load in sandbox: 30
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:browserRunner Sandbox is generated [worker #1, session #dhqtn]: http://localhost:50646/wallaby_sandbox1.html
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Preparing sandbox [worker #2, session #2fhfu]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:browserRunner Total files to load in sandbox: 29
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:browserRunner Sandbox is generated [worker #2, session #2fhfu]: http://localhost:50646/wallaby_sandbox2.html
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Preparing sandbox [worker #3, session #vvrn2]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:browserRunner Total files to load in sandbox: 26
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:browserRunner Sandbox is generated [worker #3, session #vvrn2]: http://localhost:50646/wallaby_sandbox3.html
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Preparing sandbox [worker #4, session #s1f83]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:browserRunner Total files to load in sandbox: 21
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:browserRunner Sandbox is generated [worker #4, session #s1f83]: http://localhost:50646/wallaby_sandbox4.html
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Preparing sandbox [worker #5, session #o48zp]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:browserRunner Total files to load in sandbox: 18
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:browserRunner Sandbox is generated [worker #5, session #o48zp]: http://localhost:50646/wallaby_sandbox5.html
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Prepared sandbox [worker #0, session #puape]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Prepared sandbox [worker #1, session #dhqtn]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Prepared sandbox [worker #2, session #2fhfu]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Prepared sandbox [worker #3, session #vvrn2]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Prepared sandbox [worker #4, session #s1f83]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:chromeRunner Prepared sandbox [worker #5, session #o48zp]
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:workers [worker #0, session #puape] Running tests in sandbox
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:workers [worker #1, session #dhqtn] Running tests in sandbox
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:workers [worker #2, session #2fhfu] Running tests in sandbox
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:workers [worker #3, session #vvrn2] Running tests in sandbox
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:workers [worker #4, session #s1f83] Running tests in sandbox
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:workers [worker #5, session #o48zp] Running tests in sandbox
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:middleware Preparing to serve /Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/wallaby/tracer.js
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:middleware Serving /Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/wallaby/tracer.js from disk
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:middleware Preparing to serve /jasmine@2.8.0/framework.js
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:middleware Serving /jasmine@2.8.0/framework.js from disk
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:middleware Preparing to serve /jasmine@2.1.3/configurator.js
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:middleware Serving /jasmine@2.1.3/configurator.js from disk
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:middleware Preparing to serve /jasmine@2.1.3/reporter.js
[Info] Fri, 16 Feb 2018 16:56:05 GMT wallaby:middleware Serving /jasmine@2.1.3/reporter.js from disk
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Preparing to serve /wallaby-webpack.js
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Serving /wallaby-webpack.js from cache
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Preparing to serve /____wallaby-bundle.js
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Serving /____wallaby-bundle.js from cache
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Preparing to serve /wallaby_webpack_entry.js
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Serving /wallaby_webpack_entry.js from cache
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Preparing to serve ...
...
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Preparing to serve /src/main/ui/app/shared/location-search/location-search.component.spec.js.wbp.js
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Serving /src/main/ui/app/shared/location-search/location-search.component.spec.js.wbp.js from cache
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Sandbox (active) [dhqtn] error: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js)
[Error] Runtime error: Uncaught Error: Cannot find module './src/main/ui/wallabyTest.js' (./src/main/ui/wallabyTest.js)
[Error] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Failed to map the stack to user code, entry message: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js), stack: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js)
[Info] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
...
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Preparing to serve /src/main/ui/app/features/dashlets/cancelled-complete/cancelled-complete-dashlet.component.spec.js.wbp.js
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Serving /src/main/ui/app/features/dashlets/cancelled-complete/cancelled-complete-dashlet.component.spec.js.wbp.js from cache
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Sandbox (active) [dhqtn] error: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Error] Runtime error: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Error] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Failed to map the stack to user code, entry message: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js), stack: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Info] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Preparing to serve /src/main/ui/app/features/dashlets/dashlet-title/dashlet-title.component.spec.js.wbp.js
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Serving /src/main/ui/app/features/dashlets/dashlet-title/dashlet-title.component.spec.js.wbp.js from cache
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Sandbox (active) [vvrn2] error: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js)
[Error] Runtime error: Uncaught Error: Cannot find module './src/main/ui/wallabyTest.js' (./src/main/ui/wallabyTest.js)
[Error] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Failed to map the stack to user code, entry message: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js), stack: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js)
[Info] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
...
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Preparing to serve /src/main/ui/app/features/dashlets/carrier-performance/carrier-performance.service.spec.js.wbp.js
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Serving /src/main/ui/app/features/dashlets/carrier-performance/carrier-performance.service.spec.js.wbp.js from cache
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Sandbox (active) [2fhfu] error: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js)
[Error] Runtime error: Uncaught Error: Cannot find module './src/main/ui/wallabyTest.js' (./src/main/ui/wallabyTest.js)
[Error] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Failed to map the stack to user code, entry message: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js), stack: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js)
[Info] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
...
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Preparing to serve /src/main/ui/app/utils/logger.spec.js.wbp.js
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Serving /src/main/ui/app/utils/logger.spec.js.wbp.js from cache
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Sandbox (active) [2fhfu] error: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Error] Runtime error: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Error] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Failed to map the stack to user code, entry message: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js), stack: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Info] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Sandbox (active) [vvrn2] error: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Error] Runtime error: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Error] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Failed to map the stack to user code, entry message: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js), stack: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Info] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Sandbox (active) [s1f83] error: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js)
[Error] Runtime error: Uncaught Error: Cannot find module './src/main/ui/wallabyTest.js' (./src/main/ui/wallabyTest.js)
[Error] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Failed to map the stack to user code, entry message: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js), stack: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js)
[Info] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Sandbox (active) [s1f83] error: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Error] Runtime error: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Error] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Failed to map the stack to user code, entry message: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js), stack: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Info] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Preparing to serve /____wallaby-bundle.js
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:middleware Serving /____wallaby-bundle.js from cache
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers [dhqtn] Run 0 test(s), skipped 0 test(s)
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers [2fhfu] Run 0 test(s), skipped 0 test(s)
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers [vvrn2] Run 0 test(s), skipped 0 test(s)
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers [s1f83] Run 0 test(s), skipped 0 test(s)
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers [s1f83] Sandbox is responsive, closing it
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers [dhqtn] Sandbox is responsive, closing it
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers [vvrn2] Sandbox is responsive, closing it
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers [2fhfu] Sandbox is responsive, closing it
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Sandbox (active) [o48zp] error: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js)
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Failed to map the stack to user code, entry message: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js), stack: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js)
[Info] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Sandbox (active) [o48zp] error: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Failed to map the stack to user code, entry message: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js), stack: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Info] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Sandbox (active) [puape] error: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js)
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Failed to map the stack to user code, entry message: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js), stack: Uncaught Error: Cannot find module '/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js' (/Users/me/.vscode/extensions/WallabyJs.wallaby-vscode-1.0.76/projects/bb2a4f955cb8cf0f/instrumented/src/main/ui/wallabyTest.js)
[Info] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Sandbox (active) [puape] error: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Failed to map the stack to user code, entry message: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js), stack: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Info] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Error] Runtime error: Uncaught Error: Cannot find module './src/main/ui/wallabyTest.js' (./src/main/ui/wallabyTest.js)
[Error] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Error] Runtime error: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Error] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Error] Runtime error: Uncaught Error: Cannot find module './src/main/ui/wallabyTest.js' (./src/main/ui/wallabyTest.js)
[Error] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Error] Runtime error: Uncaught Error: Cannot find module '295' (/Users/me/src/myapp/branches/me-70824-httpclient/node_modules/@angular/core/@angular/core/testing.es5.js)
[Error] at http://localhost:50646/wallaby-webpack.js?1518800165141:1
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers [o48zp] Run 0 test(s), skipped 0 test(s)
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers [o48zp] Sandbox is responsive, closing it
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers [puape] Run 0 test(s), skipped 0 test(s)
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers [puape] Sandbox is responsive, closing it
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:workers Merging parallel test run results
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:project Test run finished
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:project Processed console.log entries
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:project Processed loading sequences
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:project Processed executed tests
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:project Processed code coverage
[Info] Fri, 16 Feb 2018 16:56:06 GMT wallaby:project Test run result processed and sent to IDE
@jkyoutsey Thanks for checking!
Could you please confirm if it the the headless Chrome issue by clearing the --headless
flag passed by Wallaby to Chrome by default:
env: {
kind: 'chrome',
+ params: { runner: ' '}
},
Please also try this set of flags:
env: {
kind: 'chrome',
+ params: { runner: '--headless --disable-gpu --deterministic-fetch --disk-cache-dir=/dev/null --disk-cache-size=1'}
},
All tests DO run with
params: { runner: ' '}
All tests DO NOT run with
params: { runner: '--headless --disable-gpu --deterministic-fetch --disk-cache-dir=/dev/null --disk-cache-size=1'}
Hello @ArtemGovorov,
Unfortunately, this issue still exists in Chrome Headless (also with params: { runner: '--headless ...') Have you got any chance to investigate this problem / check with Chrome team?
@konrad300 Not yet, but the good news is that we think we have found a solution for the issue. It's already implemented and is planned to be published tomorrow. Will update the issue once the solution is released. In a meantime any of these workarounds should help.
We have implemented and published a fix that should eliminate the issue. Please update to the latest core version, and let us know how it goes. Note that wallaby cache may need to be cleared after the update before the fix works for you.
Issue description or question
Wallaby was working fine for my project, but then something happened and we started getting errors like:
Most of the runs fail, but some are OK. I need to keep adding and removing a whitespace in the spec file I'm working on to make wallaby work! This is not the productivity improvement I was expecting while buying this product.. :(
Wallaby.js configuration file
Code editor or IDE name and version
WebStorm v2017.2.5
OS name and version
OSX HighSierra 10.13.3