TravisCI tests fail on PRs
bndw opened this issue · 2 comments
bndw commented
Travis CI makes encrypted variables and data available only to pull requests coming from the same repository.
The tests relying on this are related to the S3 backend. I think the best plan is to remove the reliance on an actual AWS connection from those tests. I'll sort this out ASAP.
bndw commented
I've removed the two tests that rely on an AWS S3 connection for the time being. Moving forward, we may consider standing up a mock s3 server in TravisCI for the tests.