On Wed, Dec 10, 2014 at 10:10 AM, Maarten Hoes wrote:
>>
>> But that is a special case... making this available under tb is still
>> a valuable thing to make it easier for people running such tb-box to
>> include code coverage in the mix.
>>
> Now Im confused. Why would you want to run the same co
On Wed, Dec 10, 2014 at 4:51 PM, Norbert Thiebaud
wrote:
>
> On Wed, Dec 10, 2014 at 9:45 AM, Maarten Hoes
wrote:
> >
> > If still interested (and my tests completes as expected), I could
submit the
> > contents of my .tb directory somewhere, but im not too sure if that's
still
> > needed or rele
On Wed, Dec 10, 2014 at 9:45 AM, Maarten Hoes wrote:
>
> If still interested (and my tests completes as expected), I could submit the
> contents of my .tb directory somewhere, but im not too sure if that's still
> needed or relevant anymore with your current modifications/version of the
> script:
Hi,
On Wed, Dec 10, 2014 at 10:35 AM, Norbert Thiebaud
wrote:
>
> On Wed, Dec 10, 2014 at 3:16 AM, Maarten Hoes
wrote:
> > Hrm.
> >
> >
> > It appears I get the openldap build error when I do the build like this
> > (like it happens with the tb script) :
> >
> > $ LDFLAGS+='-fprofile-arcs'
> > $
On Wed, Dec 10, 2014 at 5:27 AM, Maarten Hoes wrote:
>
> However, doesnt the 'make it run it all in one call' implementation conflict
> at least a little with the previously stated desire to run the code coverage
> on other tests than just 'make check' ?
again being flexible does not mean that on
On Wed, Dec 10, 2014 at 7:13 AM, Maarten Hoes wrote:
> Hi ,
>
> Also,
>
> On Wed, Dec 10, 2014 at 10:40 AM, Norbert Thiebaud
> wrote:
>>
>> SRC_DIR = $(pwd)
>> BUILD=SRC
>>
> These defaults set the source and build directory to the same
> value/directory: I was under the impression that separate/
Hi ,
Also,
On Wed, Dec 10, 2014 at 10:40 AM, Norbert Thiebaud
wrote:
>
> SRC_DIR = $(pwd)
> BUILD=SRC
>
These defaults set the source and build directory to the same
value/directory: I was under the impression that separate/different source
and build dirs were a requirement ?
Anyway, just my 2
Hi,
On Wed, Dec 10, 2014 at 10:40 AM, Norbert Thiebaud
wrote:
>
> On Wed, Dec 10, 2014 at 2:29 AM, Maarten Hoes
wrote:
> > No, of course not, I guess. But the alternative to using all the
internal
> > libraries, is installing all required libraries in the right versions
> > required on the syste
ubject: Re: Scheduling lcov code coverage script
On Wed, Dec 10, 2014 at 3:16 AM, Maarten Hoes wrote:
> Hrm.
>
>
> It appears I get the openldap build error when I do the build like this
> (like it happens with the tb script) :
>
> $ LDFLAGS+='-fprofile-arcs'
&g
On Wed, Dec 10, 2014 at 2:29 AM, Maarten Hoes wrote:
> No, of course not, I guess. But the alternative to using all the internal
> libraries, is installing all required libraries in the right versions
> required on the system, and then doing --with-system-foo for all of them.
that is a trade-off
On Wed, Dec 10, 2014 at 3:16 AM, Maarten Hoes wrote:
> Hrm.
>
>
> It appears I get the openldap build error when I do the build like this
> (like it happens with the tb script) :
>
> $ LDFLAGS+='-fprofile-arcs'
> $ CFLAGS+='-fprofile-arcs -ftest-coverage'
> $ CXXFLAGS+='-fprofile-arcs -ftest-cover
Hrm.
It appears I get the openldap build error when I do the build like this
(like it happens with the tb script) :
$ LDFLAGS+='-fprofile-arcs'
$ CFLAGS+='-fprofile-arcs -ftest-coverage'
$ CXXFLAGS+='-fprofile-arcs -ftest-coverage'
$ CPPFLAGS+='-fprofile-arcs -ftest-coverage'
$ export LDFLAGS CF
On Wed, Dec 10, 2014 at 9:26 AM, Norbert Thiebaud
wrote:
> On Wed, Dec 10, 2014 at 2:20 AM, Maarten Hoes
> wrote:
> > Hi,
> >
> >
> > Thanks for the update. Ive hopped on irc for a bit, and have been
> playing
> > around with buildbot/tb for a few days for myself as well. We really
> should
> >
On Wed, Dec 10, 2014 at 2:20 AM, Maarten Hoes wrote:
> Hi,
>
>
> Thanks for the update. Ive hopped on irc for a bit, and have been playing
> around with buildbot/tb for a few days for myself as well. We really should
> talk more often. ;)
Usually I am on irc quite often (well for my time zone :-
Hi,
Thanks for the update. Ive hopped on irc for a bit, and have been playing
around with buildbot/tb for a few days for myself as well. We really should
talk more often. ;)
Unfortunately, im hitting an issue that I am unable to find a root cause
for and resolve. Im getting an internal openldap
On Tue, Dec 2, 2014 at 2:46 PM, Maarten Hoes wrote:
> Hi,
>
>
> One of the things I tried to communicate in my previous email, I perhaps may
> have tried to convey in a too subtle a manner to be noticed. So I will
> attempt to formulate it again in a slightly more explicit manner:
> ;)
>
> With th
Hi,
One of the things I tried to communicate in my previous email, I perhaps
may have tried to convey in a too subtle a manner to be noticed. So I will
attempt to formulate it again in a slightly more explicit manner:
;)
With the current state of this script, automated/scripted lcov code
coverag
Hi,
There's has been done some work recently to create a small bash shell
script to automate the creation of lcov code coverage reports of arbitrary
tests run on the libreoffice code. It can be found at
'buildbot.git/lcov-report/lcov-report.sh' [1], and it's accompanied with a
small README [2] on
18 matches
Mail list logo
