Increased testem's `browser_start_timeout` to 120s
no issue - we're seeing random failures in CI with the error "Browser failed to connect within 30s. testem.js not loaded?" - bumped the timeout to 120s to determine if it's due to occasional CI-related slowness or something else
This commit is contained in:
parent
e11fbabdaf
commit
199d33b8c0
|
@ -5,6 +5,7 @@ let launch_in_ci = [process.env.BROWSER || 'Chrome'];
|
||||||
|
|
||||||
module.exports = {
|
module.exports = {
|
||||||
framework: 'mocha',
|
framework: 'mocha',
|
||||||
|
browser_start_timeout: 120,
|
||||||
browser_disconnect_timeout: 60,
|
browser_disconnect_timeout: 60,
|
||||||
test_page: 'tests/index.html?hidepassed',
|
test_page: 'tests/index.html?hidepassed',
|
||||||
disable_watching: true,
|
disable_watching: true,
|
||||||
|
|
Loading…
Reference in New Issue