TST: enable caching on travis#5741
Conversation
|
👍 Unfortunatly it doesn't work with the Trusty environments in #5730 |
|
how badly does this overlap with what you have been doing (other than trying trusty?) with ccache + pip cache + wheelhouse it seems to go from boot -> running tests as < 2minutes. |
|
Unfortunately the trusty environment only support caching for paid instances (at the moment?) If this speeds up things significantly I am +0.5 on doing this rather than the trusty environments. The only real gain from trusty at this stage is a more up to date Texlive (2013 vs 2009) which enables us to run the pgf/xelatex tests on Travis. As I said in that PR I wish I knew more about what Travis's long term strategy is. |
|
Can you try adding a |
|
I didn't read your comment carefully enough. I have not looked into any more travis work beyond the trusty stuff and silencing some warnings here and there in the tests. |
|
@jenshnielsen I am inclined to self merge this after this round of travis passes, I want to see how much this helps master. |
|
Feel free to do that and regard this as a review if Travis is green |
|
Looks like installing wheel worked |
|
It might be worth rerunning the 3.6 job after this completes before merging to ensure that the caching of wheels works correctly and taking a note of any speed improvement for reference. |
|
I retriggered the 3.6 job. Doing bdist_wheel it took "9 min 54 sec" |
|
Doesn't look like any significant difference installing numpy etc takes 25 with and without wheel thanks to ccache but that is still much better than without caching approx 180 sec. |
TST: enable caching on travis
|
This is cool. I didn't know Travis had this feature now. We could probably also include |
No description provided.