Skip to content
This repository has been archived by the owner on Oct 10, 2021. It is now read-only.

Any idea how to add timeout ? #185

Closed
MoOx opened this issue Mar 27, 2015 · 2 comments · Fixed by #220
Closed

Any idea how to add timeout ? #185

MoOx opened this issue Mar 27, 2015 · 2 comments · Fixed by #220

Comments

@MoOx
Copy link

MoOx commented Mar 27, 2015

I am running a very "simple" file that is just a glob of some tests/*.js test files written with tape.
Everything works fine on a lot of environnements, EXCEPT (here is the fun part) on IE 10/9/8 where I am probably getting errors. That being said (I don't really know how zuul run) I am not getting breaking errors on SauceLabs (or it seems so). The immediate (and really annoying) consequence is that build stop after around 30min (which consume a lot of "credits" for private project) when some other builds take 10~20s).
Is there a way to add a timeout in order to avoid this kind of behavior (as an option) ?

@vvo
Copy link
Collaborator

vvo commented Mar 27, 2015

There is no such feature as for now if I am not mistaken.

  1. It would be a good addition
    1. Do you want a per-browser setting or a global zuul timeout?
    2. In both way it would go into zuul.yml, then read and used by
      Zuul.prototype.run = function(done) {
      , which would call .shutdown on the browser(s) when the timeout passed

Also, if you want to debug your tests on IE, either use https://github.com/xdissent/ievms. Or you can use zuul --local 8080 --ui mocha-qunit -- test.js then ngrok or localtunnel to create a public url to your local test and open it in saucelab manual IE testing sessions

@MoOx
Copy link
Author

MoOx commented Mar 27, 2015

A global option in zuul.yml lgtm.

Don't worry, I already have some VMs and I am using testem for local testing for now, it's better for my needs (handle multiple browsers easily).

vvo pushed a commit that referenced this issue Jul 1, 2015
+ add browser_output_timeout option, default to no timeout like before
So that cloud testing does not hangs when uncaught exception thrown
or any other funny thing
Related to (but also useful for anyone) tape-testing/tape#127 and
tape-testing/tape#134
This fixes #185
+ add browser_retries option, default to 6 like before
+ some more debugging information to ease .. debugging
@vvo vvo closed this as completed in #220 Jul 1, 2015
ngryman pushed a commit to ngryman/zuul that referenced this issue Jul 19, 2015
+ add browser_output_timeout option, default to no timeout like before
So that cloud testing does not hangs when uncaught exception thrown
or any other funny thing
Related to (but also useful for anyone) tape-testing/tape#127 and
tape-testing/tape#134
This fixes defunctzombie#185
+ add browser_retries option, default to 6 like before
+ some more debugging information to ease .. debugging
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants