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

test: Always run saucelabs tests locally #626

Merged
merged 2 commits into from Feb 19, 2016
Merged

test: Always run saucelabs tests locally #626

merged 2 commits into from Feb 19, 2016

Conversation

@feross
Copy link
Member

feross commented Feb 19, 2016

I think this is a simpler approach for #619. Always run the sauce labs
tests locally. If users lack the right sauce labs credentials, they’ll
get an error and hopefully set up zuul correctly before sending a PR.

feross added 2 commits Feb 19, 2016
I think this is a simpler approach for #619. Always run the sauce labs
tests locally. If users lack the right sauce labs credentials, they’ll
get an error and hopefully set up zuul correctly before sending a PR.
@feross feross changed the title test: Always run saucelabs tests lcoally test: Always run saucelabs tests locally Feb 19, 2016
@feross

This comment has been minimized.

Copy link
Member Author

feross commented Feb 19, 2016

Tests all pass. Merging!

feross added a commit that referenced this pull request Feb 19, 2016
test: Always run saucelabs tests locally
@feross feross merged commit 0210528 into master Feb 19, 2016
4 checks passed
4 checks passed
continuous-integration/appveyor/branch AppVeyor build succeeded
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
@feross feross deleted the cleanup-619 branch Feb 19, 2016
@lock

This comment has been minimized.

Copy link

lock bot commented May 4, 2018

This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue.

@lock lock bot locked as resolved and limited conversation to collaborators May 4, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked issues

Successfully merging this pull request may close these issues.

None yet

1 participant
You can’t perform that action at this time.