On Oct 4, 2012, at 14:20 , Fabien Potencier <[email protected]> wrote:
> On 10/4/12 12:09 PM, [MA]Pascal wrote: >> Lukas, >> >> Sure I can help. >> >> You don't need much memory (not more than 1G) the only problem is the >> extra time PHPunit needs to do the coverage process. > > Testing Symfony is already quite long, so making it slower is probably a bad > idea. And adding code coverage slows things down a lot. Furthermore, I don't > see the need to build the code coverage for every push. What about just > running code coverage in a cron job each day. I can setup that quite easily > and publishing the result on symfony.com should then become trivial. fine with me too. regards, Lukas Kahwe Smith [email protected] -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
