with meson, the only difference between our 'default' and 'release-ready'
builds is that the release build uses a different build type which sets
some compile/build flags. these should not provide any differing coverage
over a regular build, so we can reduce our job matrix by one here
Details
Details
- Reviewers
stefan_schmidt
Diff Detail
Diff Detail
- Repository
- rEFL core/efl
- Branch
- master
- Lint
Lint OK - Unit
No Unit Test Coverage - Build Status
Buildable 11856
Comment Actions
This looks good. A great side effect is that we would be down to 5 jobs for a push, aka the exact number of parallel jobs we can have. No more waiting. :-)
I had to rebase due my coverity change from yesterday. If CI is happy I will push it out.
Comment Actions
oh wait, it also pulls release-ready into the push builds from daily. Hope this does not impact our build time. Will know more after the CI does finish
Comment Actions
The release-ready build job needs to stay as a cron job. It is taking over 36 minutes to finish. This totally blows our nice 11 minute total time for push builds right now. :-)
The extra benefit is that we do indeed have only 5 jobs left for the push builds with this change which means all can run in parallel. :-)
There is also a break in the release build, but I do not assume this comes from this change.
| .travis.yml | ||
|---|---|---|
| 29 | This has to stay | |
Comment Actions
I got it down to 20 minutes, but it looks like something is fucking up ccache hit rate. I think I should be able to resolve this with a bit more time...
Comment Actions
Alright this is fixed in upstream meson but it'll probably be a while before the changes are available and I don't really want to be patching meson manually on CI