Best to use coverage=true only on nightly, as it gives more accurate results than release.
--Tim On Saturday, February 14, 2015 03:35:38 AM Tony Kelman wrote: > Nothing formally supported yet. Have a look at what other packages are > doing, copy them. > > We never made much progress > on https://github.com/JuliaCI/travis-build/issues/1 > or https://github.com/travis-ci/travis-ci/issues/3092 > > We can at the very least turn on the coverage=true keyword argument to > Pkg.test in the default script. That would be simple as a PR to > travis-build, dunno how long it would take them to deploy it though. This > languished because I think people were wondering whether or not to do > anything fancier, and if so exactly what it should look like. > > On Friday, February 13, 2015 at 6:45:21 PM UTC-8, Jiahao Chen wrote: > > bump > > > > So what is the currently recommended Travis CI script that generates > > coverage data? > > > > A bunch of packages have been switched over to the new scripts with > > language: julia and now have 0 coverage. See, for example: > > > > https://github.com/JuliaLang/Color.jl/issues/79 > > > > On Friday, December 12, 2014 at 6:13:55 PM UTC-5, Luthaf wrote: > >> Can it be possible to add some kind of support for code coverage ? > >> > >> I use this package (https://github.com/IainNZ/Coverage.jl) which seems > >> to be a standard one in Julia.
