Skip to content

Get Travis tests passing #352

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

Merged
merged 5 commits into from
Sep 13, 2019
Merged

Get Travis tests passing #352

merged 5 commits into from
Sep 13, 2019

Conversation

kbrock
Copy link
Contributor

@kbrock kbrock commented Sep 10, 2019

Lets get this test suite up and running again

Also, reduce the build matrix. it is currently taking many hours to build. This halves the test time

Slow for developers and uses lots of resources on travis.

Similar to #351

sure, we're running both for both all 3 runs
so not perfectly optimal, but greatly simplifies the implementation
no reason to run so many ruby versions
@kbrock
Copy link
Contributor Author

kbrock commented Sep 10, 2019

sorry for the triple push. trying to reduce build times even further

@seuros seuros merged commit 68d6dff into ClosureTree:master Sep 13, 2019
@kbrock kbrock deleted the travis branch September 16, 2019 18:33
manxingxing pushed a commit to otof-yangyu/closure_tree that referenced this pull request Oct 12, 2019
* peg sqlite3 gems

* drop ruby 2.2 and 2.3

* tell travis to run mysql and postgres

sure, we're running both for both all 3 runs
so not perfectly optimal, but greatly simplifies the implementation

* reduce the build matrix

no reason to run so many ruby versions

* add tests for 6.0
lizdeika pushed a commit to lizdeika/closure_tree that referenced this pull request Dec 3, 2019
* peg sqlite3 gems

* drop ruby 2.2 and 2.3

* tell travis to run mysql and postgres

sure, we're running both for both all 3 runs
so not perfectly optimal, but greatly simplifies the implementation

* reduce the build matrix

no reason to run so many ruby versions

* add tests for 6.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants