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

Parallelise Travis CI #32

Closed
geraintpalmer opened this issue Feb 15, 2016 · 4 comments
Closed

Parallelise Travis CI #32

geraintpalmer opened this issue Feb 15, 2016 · 4 comments

Comments

@geraintpalmer
Copy link
Member

Something like this.

https://docs.travis-ci.com/user/speeding-up-the-build/

@drvinceknight
Copy link
Contributor

If speed is (already) becoming an issue I wonder if you should perhaps think of 'downsizing' your tests (run simulation runs for shorter periods of time).

@geraintpalmer
Copy link
Member Author

Yep. I think the problem may be hypothesis generating too many things in a single test instance. May just need to reorganise the tests. This is mainly here as it would be cool and thinking about the future mostly.

@drvinceknight
Copy link
Contributor

👍

On Mon, Feb 15, 2016 at 11:56 AM Geraint Palmer notifications@github.com
wrote:

Yep. I think the problem may be hypothesis generating too many things in a
single test instance. May just need to reorganise the tests. This is mainly
here as it would be cool and thinking about the future mostly.


Reply to this email directly or view it on GitHub
#32 (comment).

@geraintpalmer
Copy link
Member Author

Discussed with @drvinceknight, Test suite fairly quick anyway: Travis parallelised for Python 2.7, 3.4, 3.5, so don't think this is worth doing.

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

No branches or pull requests

2 participants