Re: improving lcov reports

[Iago Toral <itoral igalia com>]

Hi Stefan,

thanks a lot for your feedback, I'll check this out in build.gnome.org,
likely after my holidays (which I'll start tomorrow :))... 

...but meanwhile, Alejandro, if you have time these days you can play a
little bit with Stefan's suggestion and check if this works ok for us.
The coverage reports generation is done in the module-reports.sh script.

Thanks,

Iago

On Wed, 2007-08-01 at 20:05 +0300, Stefan Kost wrote:
> hi,
> 
> I just looked at this coverage report:
> http://build.gnome.org:8080/coverage/libxml2/lcov/
> 
> imho lcov has a bug to include other sources/include in the report, but I've got
> a workaround from the lcov developers
> 
> I wonder if and where we can use this for build.gnome.org
> here is how I filter the lcov output (lcov --extract)
> 
> coverage::
> 	mkdir -p ./coverage
> 	lcov --directory . --zerocounters
> 	-$(MAKE) check
> 	lcov --directory ./src --capture --output-file ./coverage/$(PACKAGE)_tmp.info
> 	lcov --extract ./coverage/$(PACKAGE)_tmp.info "$(PWD)/src*" -o
> ./coverage/$(PACKAGE).info
> 	$(RM) ./coverage/$(PACKAGE)_tmp.info
> 	genhtml -o ./coverage --num-spaces 2 ./coverage/$(PACKAGE).info
> 
> I need to check if $(PWD) works in all cases. I can't use $(top_srcdir) as this
> is relative.
> 
> Stefan
> _______________________________________________
> Build-brigade-list mailing list
> Build-brigade-list gnome org
> http://mail.gnome.org/mailman/listinfo/build-brigade-list
>