On Thu, Jun 23, 2016 at 7:06 PM, Christian Lohmaier wrote:
> <-snip->
> should not be necessary - adjusting my $ssl_ver to TLSv1 should be
> enough;
>
> I took the liberty to change that :-)
>
> ciao
> Christian
>
Oh. Thanks. Oh well, at least I now know how to do it with mailx as well.
;)
Hi Maarten, *,
On Thu, Jun 23, 2016 at 6:37 PM, Maarten Hoes wrote:
> Hi,
>
>
> Ive taken the liberty of changing the crontab entry for the creation of the
> cppcheck report on vm140 from this :
>
> /home/buildslave/source/dev-tools/cppcheck/cppcheck-report.sh -s
> /home/buildslave/source/libo-co
Ah.
On Thu, Jun 23, 2016 at 6:37 PM, Maarten Hoes
wrote:
>
> B.)
> drop sendEmail, install mail/mailx and install&configure something like
> sendmail/postfix/exim on vm140 and see if the cppcheck-report.sh script can
> be modified to use mail/mailx instead. I do have some shell skills, so I
> c
Hi,
Ive taken the liberty of changing the crontab entry for the creation of the
cppcheck report on vm140 from this :
/home/buildslave/source/dev-tools/cppcheck/cppcheck-report.sh -s
/home/buildslave/source/libo-core -c /home/buildslave/source/cppcheck -w
/home/buildslave/tmp/www >/tmp/cppcheck-r
Caolán McNamara wrote
> On Sun, 2016-02-28 at 01:35 +,
> cppcheck.libreoffice@
>
>>> Note:
>>> The script generating this report was run at :
>>> 2016-28-02_02:35:42 with user buildslave at host vm140 as
>>> /home/buildslave/source/dev-tools/cppcheck/cppcheck-report.sh -s
>>> /
On Sun, 2016-02-28 at 01:35 +, cppcheck.libreoff...@gmail.com
> Note:
> The script generating this report was run at :
> 2016-28-02_02:35:42 with user buildslave at host vm140 as
> /home/buildslave/source/dev-tools/cppcheck/cppcheck-report.sh -s
> /home/buildslave/source/libo-core
Maarten Hoes wrote
> Hi,
>
> ...
> But I see nothing wrong with for example this link ? :
>
> http://dev-builds.libreoffice.org/cppcheck_reports/master/520.html#line-48
> ...
I don't reproduce this anymore, perhaps a temporary synchro pb.
Thanks for your feedback! :-)
Julien
--
View this mes
Hi,
Well the report was generated again last night, so there may have been
something wrong with the previous one ? (The report generator always uses
the latest git of cppcheck so there may have been an issue that has been
fixed by now.)
But I see nothing wrong with for example this link ? :
htt
Hi,
Isn't there some pb with the report? Indeed, when I click on a issue link
(in the index), it opens source code page but without the issue on it.
Julien
--
View this message in context:
http://nabble.documentfoundation.org/CppCheck-Report-Update-tp4159402p4159412.html
Sent from the Dev mai
Hi,
On Sun, Apr 26, 2015 at 10:26 PM, Maarten Hoes
wrote:
>
> Hi,
>
> On Sun, Apr 26, 2015 at 10:19 PM, Norbert Thiebaud
wrote:
> >
> > On Sun, Apr 26, 2015 at 3:00 PM, Maarten Hoes
wrote:
> > >
> > >
> > > On Sun, Apr 26, 2015 at 9:32 PM, Maarten Hoes
> > > wrote:
> > >>
> > >> I cheated, and
Hi,
On Sun, Apr 26, 2015 at 10:19 PM, Norbert Thiebaud
wrote:
>
> On Sun, Apr 26, 2015 at 3:00 PM, Maarten Hoes
wrote:
> >
> >
> > On Sun, Apr 26, 2015 at 9:32 PM, Maarten Hoes
> > wrote:
> >>
> >> I cheated, and ran 'make -k check'.
> >>
> > Oh, and assuming here now, obviously, that your issu
On Sun, Apr 26, 2015 at 3:00 PM, Maarten Hoes wrote:
>
>
> On Sun, Apr 26, 2015 at 9:32 PM, Maarten Hoes
> wrote:
>>
>> I cheated, and ran 'make -k check'.
>>
> Oh, and assuming here now, obviously, that your issue is with 'make check' ;
well yes make check fails.. but for reason very lcov relat
On Sun, Apr 26, 2015 at 9:32 PM, Maarten Hoes
wrote:
>
> I cheated, and ran 'make -k check'.
>
Oh, and assuming here now, obviously, that your issue is with 'make check'
; the rest of the lcov run was indeed successful on your vm, and I havent
got a clue what the issue may be when/if that part fai
Hi,
On Sun, Apr 26, 2015 at 9:26 PM, Norbert Thiebaud
wrote:
>
> talking about that... the lcov run has yet to finish successfully.
>
> do you mind figuring out why it does not seems to want to run when run
> under jenkins (I take it that you did successfully ran it on that box,
> right? )
>
> N
On Sun, Apr 26, 2015 at 5:29 AM, Maarten Hoes wrote:
> Hi,
>
>
> These reports havent seen an update in about two weeks. (It was scheduled to
> run weekly).
talking about that... the lcov run has yet to finish successfully.
do you mind figuring out why it does not seems to want to run when run
u
Hi,
These reports havent seen an update in about two weeks. (It was scheduled to
run weekly). It appears that the host/vm it is scheduled on
(vm140.documentfoundation.org) isnt available. Could someone please take a
look at that ?
Thanks,
- Maarten
cppcheck.libreoff...@gmail.com wrote
>
Hey,
On Sun, Mar 15, 2015 at 10:30 PM, Maarten Hoes
wrote:
> Hi,
>
>
> It appears that this job now is scheduled to run both at vm138 and at
> vm140.
> (I scheduled the run at vm140.documentfoundation.org). I really have no
> specific preference for either, but *both* may be just a little too mu
Hi,
It appears that this job now is scheduled to run both at vm138 and at vm140.
(I scheduled the run at vm140.documentfoundation.org). I really have no
specific preference for either, but *both* may be just a little too much.
Thanks,
- Maarten
--
View this message in context:
http://nab
18 matches
Mail list logo
