Parallel execution error on version 1.2.1 - "Maximum call stack size exceeded"
See original GitHub issueWhat are you trying to achieve?
Run multiple tests in parallel
What do you get instead?
RangeError: Maximum call stack size exceeded at normalizeStringWin32 (path.js:33:30) at Object.resolve (path.js:338:20) at sync (C:.…\npm\node_modules\codeceptjs\node_m odules\mkdirp\index.js:68:14) at sync (C:.…\npm\node_modules\codeceptjs\node_m odules\mkdirp\index.js:77:24) at sync (C:.…\npm\node_modules\codeceptjs\node_m odules\mkdirp\index.js:78:17) at sync (C:.…\npm\node_modules\codeceptjs\node_m odules\mkdirp\index.js:78:17) at sync (C:.…\npm\node_modules\codeceptjs\node_m odules\mkdirp\index.js:78:17) at sync (C:.…\npm\node_modules\codeceptjs\node_m odules\mkdirp\index.js:78:17) at sync (C:.…\npm\node_modules\codeceptjs\node_m odules\mkdirp\index.js:78:17) at sync (C:.…\npm\node_modules\codeceptjs\node_m odules\mkdirp\index.js:78:17) path.js:33 function normalizeStringWin32(path, allowAboveRoot) {
Seems related to #1068
Details
- CodeceptJS version: 1.2.1
- NodeJS Version: 8.9.4
- Operating System: Windows 7
- WebDriverIO Version: 4.12.0
- Configuration file:
{
"output": "./output",
"helpers": {
"WebDriverIO": {
"url": "url",
"browser": "chrome",
"host": "localhost",
"port": "4444",
"coloredLogs": true,
"restart": false,
"windowSize": "maximize",
"keepCookies": true,
"smartWait": 5000
}
},
"multiple": {
"blah": {
"chunks": 2,
"grep": "@blah"
}
},
"include": {
...
},
"mocha": {},
"bootstrap": false,
"teardown": null,
"hooks": [],
"tests": "./tests/**/*/*_test.js",
"timeout": 10000,
"name": "codecept"
}
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (3 by maintainers)
Top GitHub Comments
Just a quick thing because I have read that other people had the same issue: I added a chrome extension to my WDIO test by adding it base64 encoded to
capabilities.chromeOptions.extensions
. Due to that, I saw the following error on each exit though:Maximum call stack size exceeded
, even when the feature didn’t have any errors. The solution was to remove the extension again from the capabilities before spawning, like so:This is working for me now after upgrading to 1.3.0. Thank you