Travis optimizations#7070
Conversation
- disabled GC on running unit tests and cs fixer
- allow to run more parallel processes than CPUs
- ignore special folders ('_files' and 'AllTests') to run with phpunit
There was a problem hiding this comment.
@Ocramius What do you mean? The only PHP runtme difference is zend.enable_gc=0 and it will be ignored by HHVM.
There was a problem hiding this comment.
If it will be ignored then it's fine :)
|
Merged, thanks @marc-mabe! |
|
@marc-mabe this seems to break https://travis-ci.org/zendframework/zf2/jobs/46273266#L1171 :-( |
|
mh interesting - this error doesn't come up on my tests. |
|
It only happens on Marco Pivetta On 8 January 2015 at 09:33, Marc Bennewitz [email protected] wrote:
|
|
It's on exporting tested results of Zend\Math and it has 312585 assertions. |
|
Probably due to RNG tests... Those could be put in ignored coverage... |
|
test coverage should not be ignored only because it's slow |
|
@marc-mabe repeatedly stress-testing the same segment of code during a statistical benchmark isn't really useful for us (for the purpose of coverage) |
|
the problem is that this test isn't only a stress test. It would be optimal to reduce the cycles for rnd stress test to be 1 to be a normal unit test. EDIT: Doesn't work |
|
@marc-mabe isn't |
|
@Ocramius Good idea but even with Results on running So I think gc needs to be enabled on running phpunit and the biggest slow down is code coverage generation. Btw. the cs fixer is ~ 1-5% faster with gc off |
…ance-optimizations-via-gc-collection-disabled' Close zendframework/zendframework#7070
…ance-optimizations-via-gc-collection-disabled' into develop Close zendframework/zendframework#7070 Forward port zendframework/zendframework#7070
This should be make little performance improvements.
A much better performance improvement would be to run all unit tests and cs fixer in parallel, too.
But I currently haven't a good idea how to do that simplified.