split Travis into parallel test suites #7773
Conversation
This will speed up builds by several minutes, but we will have to clear the cache when dependencies are updated. See https://docs.travis-ci.com/user/caching/#Clearing-Caches
|
https://travis-ci.org/brave/browser-laptop/builds/212314661 finished in 32 minutes (much of which was waiting for jobs to start) so it's like a 15min improvement |
There was a problem hiding this comment.
++ looks great to me! 😄 Only concern I have would be: what's a good "path of least resistance" way to take care of clearing the cache? If we can't solve that, I would suggest removing that commit for now (and creating an issue which captures the config and the challenge we face)
|
@bsclifton i think we will generally only need to clear the cache when changing the runtime environment (ex: upgrading Node), so it should be fine. to be extra safe, we can use shrinkwrap. https://docs.npmjs.com/cli/shrinkwrap |
|
@diracdeltas ah nice! 😄 In that case, let's merge 🎉 |
…s-ci with brave#7773 and this broke the `uitest` task. Since the unit tests run quickly and `npm run unittest` still works great, this task isn't really needed anymore. Auditors: @NejcZdovc, @diracdeltas
Breaks it up so we can run 9 test suites in parallel. Also caches NPM dependencies so that these are not re-downloaded for every test suite.
Test Plan:
N/A