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

TravisCI Builds Failing #213

Closed
joshbuker opened this issue Nov 27, 2019 · 5 comments · Fixed by #214
Closed

TravisCI Builds Failing #213

joshbuker opened this issue Nov 27, 2019 · 5 comments · Fixed by #214
Labels
help wanted Community assistance requested

Comments

@joshbuker
Copy link
Member

It appears the configuration for the test database creation needs to be updated for TravisCI. All builds are failing due to the following error:

$ mysql -e 'create database sorcery_test;'

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)

The command "mysql -e 'create database sorcery_test;'" failed and exited with 1 during .
@joshbuker joshbuker added the help wanted Community assistance requested label Nov 27, 2019
@mladenilic
Copy link
Contributor

Can we just remove the command from the travis.yml? Based on spec app, sqlite is used – https://github.com/Sorcery/sorcery/blob/master/spec/rails_app/config/database.yml

@joshbuker
Copy link
Member Author

Interesting, that might be specific to the app within the specs but it's worth a shot regardless.

@joshbuker
Copy link
Member Author

So that resolves the database error, and now it's just stuck on sprockets expecting a manifest file. I think there might be a PR or Issue floating around for that (sprockets 4 breaking things).

@mladenilic
Copy link
Contributor

I already replied on the PR ;)

#214 (comment)

@joshbuker
Copy link
Member Author

Perfect! Thanks @mladenilic and @Plsr!

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

Successfully merging a pull request may close this issue.

2 participants