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

Consistently use error log level when connecting fails #952

Merged
merged 1 commit into from Feb 11, 2018

Conversation

Projects
None yet
2 participants
@RasmusWL
Contributor

RasmusWL commented Feb 9, 2018

Fixes #943

@RasmusWL

This comment has been minimized.

Contributor

RasmusWL commented Feb 9, 2018

closing and reopening to make Travis rerun the tests.

The travis build step 1255.8 (coverage) failed to do aws s3 cp --recursive s3://com-gavinroy-travis/pika/$TRAVIS_BUILD_NUMBER/ coverage

@RasmusWL RasmusWL closed this Feb 9, 2018

@RasmusWL RasmusWL reopened this Feb 9, 2018

@RasmusWL

This comment has been minimized.

Contributor

RasmusWL commented Feb 9, 2018

Okay, coverage step failed again on Travis. Hopefully you guys can help out :)

Looking at the log again, I can see that the real error is probably the credentials:

$ aws s3 cp --recursive s3://com-gavinroy-travis/pika/$TRAVIS_BUILD_NUMBER/ coverage
fatal error: Unable to locate credentials

@lukebakken lukebakken added this to the 1.0.0 milestone Feb 11, 2018

@lukebakken lukebakken self-assigned this Feb 11, 2018

@lukebakken lukebakken merged commit 83a5ab4 into pika:master Feb 11, 2018

1 of 2 checks passed

continuous-integration/travis-ci/pr The Travis CI build failed
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
@lukebakken

This comment has been minimized.

Contributor

lukebakken commented Feb 11, 2018

Thanks!

lukebakken added a commit that referenced this pull request Apr 12, 2018

lukebakken added a commit that referenced this pull request Apr 13, 2018

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