Timeouts when running more then one page per worker on Travis

[jzaefferer]

I've working on integrating browserstack-runner into QUnit builds on Travis, using simple obfuscation to embed credentials to allow runs against pull requests, without making it too easy to find the credentials. The configuration sets up 14 workers to run 4 test pages, which works fine locally. When running on Travis, each worker runs the first page, then fails to change the URL and eventually times out. I pushed another commit to the same branch to verify the result, and got the same failure - all 14 workers time out after running one page.

Since the same setup works fine locally I have no clue what the issue is. There are no errors displayed in the Travis output and the BrowserStack build page doesn't show anything either. Looking for some ideas how to debug or better yet, solve this.

[jzaefferer]

@dhimil @nakula since I somewhat got your attention, this and other timeout issues are a massive blocker for really using this tool. Since I have very limited access to your infrastructure, it would be of massive and important help if you could spend time on it. Meanwhile I'm trying to help with everything else to get this tool to a 1.0.0 release.

[jzaefferer]

@dhimil @nakula could you look into this again?

[jzaefferer]

I just tried this again and got the same result, using browserstack-runner 0.2.0. All runners time out after the first URL is done. Maybe one of the changes in master will help, still need a published release to test that.

[nakula]

oops. let me publish it.

On Fri, Nov 7, 2014 at 5:20 PM, Jörn Zaefferer notifications@github.com
wrote:

I just tried this again and got the same result, using browserstack-runner
0.2.0. All runners time out after the first URL is done. Maybe one of the
changes in master will help, still need a published release to test that.

—
Reply to this email directly or view it on GitHub
#95 (comment)
.

regards
Nakul Aggarwal
www.browserstack.com

[nakula]

just added you as author and published a new version as well :-)

On Fri, Nov 7, 2014 at 5:24 PM, Nakul Aggarwal nakula@gmail.com wrote:

oops. let me publish it.

On Fri, Nov 7, 2014 at 5:20 PM, Jörn Zaefferer notifications@github.com
wrote:

I just tried this again and got the same result, using
browserstack-runner 0.2.0. All runners time out after the first URL is
done. Maybe one of the changes in master will help, still need a published
release to test that.

—
Reply to this email directly or view it on GitHub
#95 (comment)
.

regards
Nakul Aggarwal
www.browserstack.com

regards
Nakul Aggarwal
www.browserstack.com

[jzaefferer]

Thanks. Just tried again with 0.2.1, still fails to change URLs, see https://travis-ci.org/jzaefferer/qunit/builds/40286418 and https://www.browserstack.com/automate/builds/2ee5c348dde5aae31f822dc4ba573492cfdeccfc/sessions/bd6a4f2ad78fba7e10c597f6359707fb53bdb518

If you have access to the latter, you can see that it took two screenshots, one for the first page as intended, another one of the same page. Apparently the first page finishes, it takes the screenshot, then the changeUrl call doesn't do anything and it just sits there for five minutes, doing nothing. Until it times out, screenshots the same page again and errors out.

If that was happening locally I could debug it, but it only happens for me on Travis. One test run takes at least five minutes, and I have no clue what is going wrong.

Can you check if the API call to change the URL is received? May there's an error somewhere that isn't shown in the Travis build output?

[nakula]

there should be change url call as well on dashboard, which possibly means
it was never fired. can we log "change url" call in travis as well?

On Fri, Nov 7, 2014 at 6:06 PM, Jörn Zaefferer notifications@github.com
wrote:

Thanks. Just tried again with 0.2.1, still fails to change URLs, see
https://travis-ci.org/jzaefferer/qunit/builds/40286418 and
https://www.browserstack.com/automate/builds/2ee5c348dde5aae31f822dc4ba573492cfdeccfc/sessions/bd6a4f2ad78fba7e10c597f6359707fb53bdb518

If you have access to the latter, you can see that it took two
screenshots, one for the first page as intended, another one of the same
page. Apparently the first page finishes, it takes the screenshot, then the
changeUrl call doesn't do anything and it just sits there for five minutes,
doing nothing. Until it times out, screenshots the same page again and
errors out.

If that was happening locally I could debug it, but it only happens for me
on Travis. One test run takes at least five minutes, and I have no clue
what is going wrong.

Can you check if the API call to change the URL is received? May there's
an error somewhere that isn't shown in the Travis build output?

—
Reply to this email directly or view it on GitHub
#95 (comment)
.

regards
Nakul Aggarwal
www.browserstack.com

[jzaefferer]

I just tried this again, with a different result, but still not successful. Here's the Travis build: https://travis-ci.org/jzaefferer/qunit/builds/43829326 and the BrowserStack build: https://www.browserstack.com/automate/builds/0648827dc42c85f29417305dac42301922529127

Safari 7 and 8, both on OSX, finished in under 20 seconds. Opera 25 on Windows 7 finished in about a minute, still okay. The others all timed out, e.g. Chrome 39: https://www.browserstack.com/automate/builds/0648827dc42c85f29417305dac42301922529127/sessions/b7150a2ebc9a8b0de40b71a4d0f3d15b7502c0ff

In contrast to earlier attempts, changing the page worked, but in the browsers with timeouts, the second page failed to load. The screenshots all show something along the lines of "unable to connect" or "page failed to load". @nakula ideas?

[jzaefferer]

I don't know what changed, but this is now working well.