Hello, On 4 oct. 2012, at 14:04, Lukas Kahwe Smith <[email protected]> wrote:
> > On Oct 4, 2012, at 12:09 , "[MA]Pascal" <[email protected]> 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. > > ok then it should work right now already. > >> Uploading the result of the coverage is one thing but how can we trace it >> inside the travisci build ? I mean how to link the build to the webpage of >> the coverage. > > we have access the the following two env variables: TRAVIS_BRANCH and > TRAVIS_JOB_ID > we should then be able to upload the files to an URL that includes the job id > and then output the url to the console at the end. > in theory we could even add the URL as a comment on the commit on github > >> Do we need to store history of the coverage or we only need a static repo >> (coverage.symfony.com) with the very last successfully uploaded coverage >> result ? > > i would at least keep the data of the last week(s) and maybe one from every > month .. > but i also dont know how much space they need and how much space we have > available. > >> Another question : do you know if it's possible to generate coverage using >> the merge of multiple PHPUnit processes ? I explain myself : you can have >> specific testCase for PHP5.4 which would be covered only in the 5.4 >> travis-ci job but won't be in the others, so those classes won't have their >> 100% coverage even it's covered overall. > > i dont really think we need to worry about that. if necessary we can add > comments to make it clear that a given class/method requires a specific php > version. we shouldnt obsess about the exact code coverage numbers. it could become more interesting in case of a windows build (cf Process component) > > 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 -- 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
