Not too confused at least, check out this: https://coveralls.io/builds/1128440 You can see it shows the two "jobs". Which one you get for the badge... unclear to me, possibly configurable?
On Monday, August 25, 2014 10:25:42 PM UTC-4, Elliot Saba wrote: > > Ah, that I have no idea. > -E > > > On Mon, Aug 25, 2014 at 10:20 PM, Tim Holy <[email protected] > <javascript:>> wrote: > >> In partiuclar, Coveralls won't get confused if we push both? >> >> --Tim >> >> On Monday, August 25, 2014 10:10:10 PM Elliot Saba wrote: >> > Only if there are features you need that exist in one and not the >> other, I >> > suppose. >> > -E >> > >> > On Mon, Aug 25, 2014 at 10:07 PM, Tim Holy <[email protected] >> <javascript:>> wrote: >> > > Once nightly and release become different again, will we need to >> reinstate >> > > the >> > > if clauses? >> > > >> > > --Tim >> > > >> > > On Monday, August 25, 2014 06:45:41 PM Iain Dunning wrote: >> > > > Check what I just did for HttpCommon, only thing lacking is a >> Pkg.build >> > > > >> > > > https://github.com/JuliaLang/HttpCommon.jl/blob/master/.travis.yml >> > > > >> > > > script: >> > > > - julia -e 'Pkg.init(); Pkg.clone(pwd())' >> > > > - julia -e 'Pkg.test("HttpCommon", coverage=true)' >> > > > after_success: >> > > > - julia -e 'cd(Pkg.dir("HttpCommon")); Pkg.add("Coverage"); using >> > > >> > > Coverage; >> > > >> > > > Coveralls.submit(Coveralls.process_folder())' >> > > > >> > > > This what I hope to see most packages look like now >> > > > >> > > > On Monday, August 25, 2014 7:52:21 PM UTC-4, Elliot Saba wrote: >> > > > > I think that should be considered a bug, since clone() calls >> resolve() >> > > > > which calls build()..... but only for the stuff that resolve() >> thinks >> > > >> > > has >> > > >> > > > > changed. We should probably just call build() after resolve() in >> > > >> > > clone. >> > > >> > > > > -E >> >> >
