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

Failed builds due to grunt-saucelabs error #1279

Closed
mstred opened this Issue Aug 17, 2015 · 3 comments

Comments

Projects
None yet
3 participants
@mstred
Member

mstred commented Aug 17, 2015

Hi All,

I've seen that my latest PR build on Travis CI hasn't been OK due to an error in grunt saucelabs-test task, but I guess this actually doesn't relate only to my commits.

From the project's PR page, we can see that the first pull request build failed was #1222. From that build log, there's this error at the bottom of the page:

$ grunt saucelabs-test
Running "connect:all" (connect) task
Started connect web server on http://localhost:3000
Running "saucelabs-qunit:all" (saucelabs-qunit) task
=> Starting Tunnel to Sauce Labs
=> Stopping Tunnel to Sauce Labs
>> 
>> Error closing tunnel
No output has been received in the last 10 minutes, this potentially indicates a stalled build or something wrong with the build itself.
The build has been terminated

I suggest we should disable this task temporarily in Gruntfile.js, but I'm opening this issue to let us discuss a better solution for that.

@outsideris

This comment has been minimized.

Show comment
Hide comment
@outsideris

outsideris Aug 18, 2015

Member

Thank you for reporting. It looks like permission issue. We are digging it.

Member

outsideris commented Aug 18, 2015

Thank you for reporting. It looks like permission issue. We are digging it.

outsideris added a commit to outsideris/summernote that referenced this issue Aug 18, 2015

diablse sauce labs tests on pull request
* refer <http://docs.travis-ci.com/user/pull-requests/>
* For security reason, travis build for PR can't use
  encrypted data or environment variables. So, tests in
  sauce labs can't run on PR. See details in
  <travis-ci/travis-ci#1946>
* close #1279

outsideris added a commit to outsideris/summernote that referenced this issue Aug 18, 2015

diablse sauce labs tests on pull request
* refer <http://docs.travis-ci.com/user/pull-requests/>
* For security reason, travis build for PR can't use
  encrypted data or environment variables. So, tests in
  sauce labs can't run on PR. See details in
  <travis-ci/travis-ci#1946>
* close #1279

outsideris added a commit to outsideris/summernote that referenced this issue Aug 18, 2015

diablse sauce labs tests on pull request
* refer <http://docs.travis-ci.com/user/pull-requests/>
* For security reason, travis build for PR can't use
  encrypted data or environment variables. So, tests in
  sauce labs can't run on PR. See details in
  <travis-ci/travis-ci#1946>
* close #1279

outsideris added a commit to outsideris/summernote that referenced this issue Aug 18, 2015

diablse sauce labs tests on pull request
* refer <http://docs.travis-ci.com/user/pull-requests/>
* For security reason, travis build for PR can't use
  encrypted data or environment variables. So, tests in
  sauce labs can't run on PR. See details in
  <travis-ci/travis-ci#1946>
* close #1279
@outsideris

This comment has been minimized.

Show comment
Hide comment
@outsideris

outsideris Aug 18, 2015

Member

@mstred We skip saucelabs for build on PR. You can pass the build if you rebase your PR against develop branch.

Member

outsideris commented Aug 18, 2015

@mstred We skip saucelabs for build on PR. You can pass the build if you rebase your PR against develop branch.

@hackerwins

This comment has been minimized.

Show comment
Hide comment
@hackerwins
Member

hackerwins commented Aug 18, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment