Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Finishing command for sauce labs #6

Open
cupito opened this issue Jun 24, 2014 · 4 comments
Open

Finishing command for sauce labs #6

cupito opened this issue Jun 24, 2014 · 4 comments
Assignees
Labels

Comments

@cupito
Copy link

cupito commented Jun 24, 2014

Seems that the tests do not send a term signal to sauce labs. I can see Test did not see a new command for 90 seconds. Timing out. for every test send with dalekjs. Due to the fact that the accounts are time based, it's maybe not the best way for waste money. Can a finishing signal send to saucelabs?

@asciidisco
Copy link
Member

Damn. That is a huge bug, thanks for finding.
We will take care of it asap.

@asciidisco asciidisco added the bug label Jun 28, 2014
@asciidisco asciidisco self-assigned this Jun 28, 2014
@marsch
Copy link
Contributor

marsch commented Aug 29, 2014

@cupito mhh i have the same problem and I basically think that only happens if a test isn't finished with .done() - which happens when a command isn't found for me its .setValue() - which isn't implemented in the sauce-driver yet

@asciidisco is that right? any thought?

@jonpreston
Copy link

I'd really love to be able to use sauce for my test suite, but this is a major blocker. Any updates?

@amitaibu
Copy link

I have a test that used done(), but still face this issue -- it seems related to using the screenshot() command,

#10 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants