Yeah. All lines that get run are 0, and all untested lines remain at `-`. My backtraces all look fine (at least I haven't noticed anything weird).
Platform is x86_64 arch linux, running 8 day old master, commit eea31ae*. I can replicate this in a small testable case by creating a small script, and running it with coverage, so it's not specific to my package. On Thu, Jan 22, 2015 at 5:31 PM, Tim Holy <[email protected]> wrote: > Are you saying that no line has anything higher than a 1 in front of it? > > I just tried the procedure you described below, as well as the simpler > `Pkg.test("Control", coverage=true)` (which now works on julia 0.4 again, > if > you're up to date). Both approaches worked fine for me. Do you have any > problems with your backtraces, or anything else potentially related? What's > your platform? > > --Tim > > On Thursday, January 22, 2015 11:52:17 AM James Crist wrote: > > I'm having issues getting coverage to work. Here's what I'm doing: > > > > 1. From my package directory I run this: > > > > $ julia --code-coverage --inline=no test/runtests.jl > > > > This results in *.cov files for all files that are run. > > > > 2. Run julia, then: > > > > julia> using Coverage > > julia> coverage_folder() > > > > This prints out a list of files in my src folder. All files that have > *.cov > > associated with them also show "Skipped file_name". > > > > Looking closer at the *.cov files, I see that all lines that *I know* are > > run have a 0 next to them, even if they are run several several times in > > the tests. Lines that have no coverage are still at `-`. Any idea why? > I'm > > kind of baffled on this. > > > > The package in question: https://github.com/JuliaControl/Control.jl > >
