Re: Review requested: updated gcov/lcov report shell script

would be appreciated here. Thanks, - Maarten [1] https://gerrit.libreoffice.org/c/buildbot/+/135560 On Thu, Jun 9, 2022 at 5:55 PM Maarten Hoes wrote: > Hi, > > > After my previous emails on the gcov/lcov code coverage subject on this > list, I have modified the existing l

Review requested: updated gcov/lcov report shell script

Hi, After my previous emails on the gcov/lcov code coverage subject on this list, I have modified the existing lcov html report generating script [1], and would like some feedback/reviewer on the modifications. The major changes compared to the previous version are: 1.) The script was reworked

Re: How to clone/commit/push (for 'buildbot' repo) ?

On Thu, Jun 9, 2022 at 4:20 PM Maarten Hoes wrote: > > What I think I see happening is that the client is trying to force 'sftp' > when the scp command is used, and the server is not having it ? Or perhaps > I am simply using the wrong command to clone the repo and set it up for

How to clone/commit/push (for 'buildbot' repo) ?

Hi, I made some modifications to the lcov report script (and the accompanying README) in the buildbot repo, but I am having problems with putting the modified version up for review. I am probably doing things the wrong way, so perhaps it's best if I just show what I am doing here. I saw a few

Re: 'make check' fails when building with gcov code coverage

On Wed, Jun 1, 2022 at 5:22 PM Stephan Bergmann wrote: > > I agree with you that the status quo would not be useful (and don't > think you are annoying in any way). > > I still strongly (but naively, without digging into the code in any way) > assume that those tests are not failing for you all

Re: 'make check' fails when building with gcov code coverage

Hi, On Tue, May 31, 2022 at 2:07 PM Stephan Bergmann wrote: > So the general advice would be to ignore occasional failed builds (which > might not only fail due to spurious test failures, but also because e.g. > a build breaker got submitted by accident). If some specific tests > cause enough

Re: 'make check' fails when building with gcov code coverage

Hi, On Mon, May 30, 2022 at 10:03 AM Stephan Bergmann wrote: > On 25/05/2022 14:38, Maarten Hoes wrote: > > gb_GCOV=YES verbose=t make UITest_solver > > gb_GCOV=YES verbose=t make CppunitTest_sccomp_solver > > gb_GCOV=YES verbose=t make CppunitTest_sccomp_swarmso

Re: 'make check' fails when building with gcov code coverage

i, May 27, 2022 at 10:26:21AM +0200, Maarten Hoes < > hoes.maar...@gmail.com> wrote: > > CFLAGS='-fprofile-arcs -ftest-coverage' CXXFLAGS='-fprofile-arcs > > -ftest-coverage' LDFLAGS='-fprofile-arcs -lgcov' ./autogen.sh > > --enable-python=internal --without-system-libs --wi

Re: 'make check' fails when building with gcov code coverage

On Fri, May 27, 2022 at 8:13 AM Miklos Vajna wrote: > Hi Maarten, > > On Wed, May 25, 2022 at 02:38:27PM +0200, Maarten Hoes < > hoes.maar...@gmail.com> wrote: > > I've been trying to run 'make check' in combination with building > > LibreOffice with gcov c

'make check' fails when building with gcov code coverage

Hi, I've been trying to run 'make check' in combination with building LibreOffice with gcov code coverage, and get failures for the following tests : gb_GCOV=YES verbose=t make UITest_solver gb_GCOV=YES verbose=t make CppunitTest_sccomp_solver gb_GCOV=YES verbose=t make

Re: Compiling LO for lcov/gcov code coverage fails (gb_GCOV=YES)

On Tue, May 17, 2022 at 10:53 AM Michael Stahl wrote: > On 15.05.22 15:00, Maarten Hoes wrote: > > I guess that 'git bisect run' considers things a 'success' if the build > > succeeds (zero exit code), and a 'failure' if the build fails (non zero > > exit code).

Re: Compiling LO for lcov/gcov code coverage fails (gb_GCOV=YES)

On Tue, May 17, 2022 at 11:42 AM Michael Stahl wrote: > On 13.05.22 16:42, Maarten Hoes wrote: > > So to sum it up, with only gcc installed, the gcov build works if I > modify : > > > > external/expat/ExternalProject_expat.mk > > external/liborcus/ExternalProje

Re: Compiling LO for lcov/gcov code coverage fails (gb_GCOV=YES)

On Sun, May 15, 2022 at 3:00 PM Maarten Hoes wrote: > > I guess that 'git bisect run' considers things a 'success' if the build > succeeds (zero exit code), and a 'failure' if the build fails (non zero > exit code). Duh. But I don't get the impression that it matters to git what

Re: Compiling LO for lcov/gcov code coverage fails (gb_GCOV=YES)

Hi, On Wed, May 11, 2022 at 9:07 PM Thorsten Behrens wrote: > Hi Maarten, > > Maarten Hoes wrote: > > I personally do not know enough about the build system to figure out how > to > > correct this. Any and all help in trying to make this work again would be > >

Re: Compiling LO for lcov/gcov code coverage fails (gb_GCOV=YES)

On Fri, May 13, 2022 at 4:42 PM Maarten Hoes wrote: > > Judging by the comments, it looks like clang for skia is only enforced on > Windows and Mac (comment : '#Skia is the default on Windows and Mac, so > hard-require Clang.', around line 12177 in configure.ac). > > Sorry,

Re: Compiling LO for lcov/gcov code coverage fails (gb_GCOV=YES)

On Fri, May 13, 2022 at 3:06 PM Stephan Bergmann wrote: > Just performance, I think. Luboš should know the details. > Ok. Then for my use case, it would not really be that much of an issue to compile with gcc instead. Maybe your solution for now is --disable-skia? > Perhaps, or at least a

Re: Compiling LO for lcov/gcov code coverage fails (gb_GCOV=YES)

On Fri, May 13, 2022 at 10:37 AM Stephan Bergmann wrote: > On 5/12/22 15:44, Maarten Hoes wrote: > > What I *think* I see happening, is that the '-fprofile-arcs > > -ftest-coverage -lgcov' flags are correctly being set on the > > commandlines, up until were the error occu

Re: Compiling LO for lcov/gcov code coverage fails (gb_GCOV=YES)

On Thu, May 12, 2022 at 8:47 AM Stephan Bergmann wrote: > On 5/11/22 21:07, Maarten Hoes wrote: > > I also added '--with-parallelism=1' to ./autogen.sh, to make the output > > of 'make' a little clearer and easier to read. > > ...or, for a parallelizing make invocation, pa

Re: Compiling LO for lcov/gcov code coverage fails (gb_GCOV=YES)

On Thu, May 12, 2022 at 8:42 AM Stephan Bergmann wrote: > On 5/11/22 21:07, Maarten Hoes wrote: > > I just noticed: reading back the error more carefully, I noticed it's > > clang that generated the error, even though I didn't specifically tried > > to compile with cla

Re: Compiling LO for lcov/gcov code coverage fails (gb_GCOV=YES)

Ah. I added the flags to 2 files, listed below, and rebuild. It builds now. I'm not too sure if the edits below are entirely placed in the right way or in the right place, but it does make the build work ;) external/liborcus/ExternalProject_liborcus.mk external/expat/ExternalProject_expat.mk

Re: Compiling LO for lcov/gcov code coverage fails (gb_GCOV=YES)

me/maarten/src/libreoffice/core/workdir/ExternalProject/liborcus/build] Error 2 make: Leaving directory '/home/maarten/src/libreoffice/core/external' On Wed, May 11, 2022 at 7:28 PM Luboš Luňák wrote: > On Wednesday 11 of May 2022, Maarten Hoes wrote: > > Hi, > > > > >

Compiling LO for lcov/gcov code coverage fails (gb_GCOV=YES)

Hi, I'm trying to build LibreOffice on Linux (Fedora 36) with the appropriate flags set for 'lcov/gcov code coverage' (how many / which lines of the codebase get executed by running the test suite 'make check'). Normally you would set the appropriate CFLAGS / LDFLAGS (-fprofile-arcs

Re: CppCheck Report on vm140 Not Running

Hi, On Thu, Apr 29, 2021 at 7:30 PM Guilhem Moulin wrote: > On Thu, 29 Apr 2021 at 15:53:46 +, Luke Benes wrote: > > At the time, Maarten reported this on the dev IRC, infra IRC, and the > > mailing list. At the time, I assumed someone from infra would take > > care of it. > > As cloph

Re: CppCheck Report on vm140 Not Running

Hi, I wasn't subscribed to the dev mailing list up until just now, so when people stopped explicitly CC'ing me I missed some parts of this discussion. So here are some of my thoughts on the matter. I personally feel that if there is little interest in running cppcheck on the entire codebase

Re: CppCheck Report on vm140 Not Running

Now that I think of it, On Thu, Apr 22, 2021 at 2:51 PM Luke Benes wrote: > > I'm more interested in running such tools locally > > Depending on the configuration, cppcheck scans can take 8+ hours to run. > > That may be true when running cppcheck on the entire codebase, but I now assume

Re: CppCheck Report on vm140 Not Running

Hi, On Thu, Apr 22, 2021 at 9:14 AM Miklos Vajna wrote: > I'm more interested in running such tools locally > > < - snip -> > > The other problem with cppcheck is that it doesn't build on an existing > c++ parser from a compiler (not based on e.g. gcc or clang), so its > signal/noise ratio is

Re: Gmail marks it as spam

Hi Ilmari, On Wed, Nov 11, 2020 at 8:32 AM Ilmari Lauhakangas < ilmari.lauhakan...@libreoffice.org> wrote: > Here is a bigger hammer for whitelisting addresses in gmail: > > https://www.lifewire.com/how-to-whitelist-a-sender-or-domain-in-gmail-1172106 > Yeah, I guess there are things an

Re: Gmail marks it as spam

Hi Julien, On Tue, Nov 10, 2020 at 10:28 PM Julien Nabet wrote: > > I suppose it's because of "yahoo.fr". Indeed, I can't do anything about > mail policy but don't worry I don't send regularly messages on dev forum > :-) > > When I open a thread, I check on > >

Gmail marks it as spam (was: Try to upgrade to Firebird 3.0.7)

Hi julien2412, I'm not quite sure if this is anything anyone can do anything about, but I still feel like stating here: For quite a while now, all of the posts of you to the libreoffice dev mailing list gets put into my 'spam' folder by gmail/google. All of the posts to the same list by other

Automated cppcheck reports not running ?

Hi, I noticed that the automated cppcheck report script [1] no longer appears to be running. When I look at the website that hosts the html reports [2], then the last time the script was run was about mid- June. When I look at the last automated email that was sent to this list [3] (to notify

[Libreoffice-commits] dev-tools.git: scan-build-report/README scan-build-report/scan-build-report.sh

scan-build-report/README | 24 scan-build-report/scan-build-report.sh | 169 + 2 files changed, 193 insertions(+) New commits: commit 792d261fd250e23d863c4a9d044b08e173e3bd53 Author: Maarten Hoes AuthorDate: Thu Oct 15 13:23:39 2020

Re: llvm/clang static analyzer reports

Hi, On Thu, Oct 15, 2020 at 6:51 PM Stephan Bergmann wrote: > On 15/10/2020 10:58, Stephan Bergmann wrote: > > On 15/10/2020 09:51, Maarten Hoes wrote: > >> Just one more thing I need to mention. At some point during the > >> build/analysis, I run into the follow

Re: llvm/clang static analyzer reports

Hi, On Thu, Oct 15, 2020 at 10:58 AM Stephan Bergmann wrote: > > We can have a look once you have sent something to Gerrit. > > Ok. I put it up for review: https://gerrit.libreoffice.org/c/dev-tools/+/104372 As requested, I added you as a reviewer. - Maarten

Re: llvm/clang static analyzer reports

Hi, On Thu, Oct 15, 2020 at 8:48 AM Stephan Bergmann wrote: > Sure, can't hurt to document the approach you've taken. So if that's > not much additional work, sounds good to me to add a script to > dev-tools. You can add me as reviewer. Alright, I'll do that then. Just one more thing I

Re: llvm/clang static analyzer reports

in advance, - Maarten Hoes. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: llvm/clang static analyzer reports

Hi, On Thu, Oct 1, 2020 at 8:59 AM Stephan Bergmann wrote: We would need some mechanism to filter > out such identified false positives, with whatever mechanism would be > suitable: an annotation in the source code, a modification of the > -analyzer-... command line options passed to clang,

llvm/clang static analyzer reports

instead of listing all of them, so something must be going wrong here. For what it's worth: the entire run took about 4 hours to complete on my system (Intel Core i7-10700, 32GB RAM) Sincerely, Maarten Hoes [1] https://bugs.documentfoundation.org/show_bug.cgi?id=39596 [2] https

Re: Cppcheck: Reduction of False Positives: Manual Approach

Hi, On Sun, Sep 30, 2018 at 5:20 AM Luke Benes wrote: > Maarten, > Thanks for your suggestion here and your earlier contributions to the > Cppcheck Report. I agree that we should create the include file > dynamically. However the approach used by your script seems like overkill. > Cppcheck

Re: Cppcheck: Reduction of False Positives: Manual Approach

Hi, On Sun, Sep 30, 2018 at 11:29 AM Tamás Zolnai wrote: > > I'm not sure what your modification is doing. I just checked the report > you attached and I compared it with the full report and I see your change > filters out not only false positives. > > Am I interpreting correctly here that the

Re: Best way to handle oddball header #includes for Cppcheck Report?

Hi, sberg wrote > I'm not sure how useful this is, overall. Apparently, Cppcheck is run > on .cxx files without knowledge of the specific -I, -D, etc. compiler > switches that our build system would pass to the compiler for a given > .cxx file. That will always lead to issues (Cppcheck not

Re: Cppcheck: Reduction of False Positives: Manual Approach

Hi, slacka wrote > Ideally, the next step would be to extract the "DEFS": and "INCLUDE": from > gbuild-to-ide and pass that to cppcheck. But that's for another time. Well, the very name 'gbuild-to-ide' sounds intriguing, but I can't figure out what it is supposed to do (and how could it help

Re: Cppcheck: Reduction of False Positives: Manual Approach

they are located in, and 'sort -u' to mention each directory just once. Would that be sufficient for your suggested modifications ? - Maarten Hoes #!/bin/sh TMPFILE=/tmp/tmpfile.txt INCLUDEFILE=/tmp/incfile.txt rm -f "$TMPFILE" find . -type f \( -name \*.hxx -o -name \*.h \) | \ while re

Cppcheck reports: email notifications

Hi, I noticed that the weekly scheduled 'cppcheck report update' email notification of the March 26 run dint appear on this (dev) mailing list. Upon investigation it turns out that the job ran correctly, but that the email message was held (Your message to LibreOffice awaits moderator approval)

License Statement

All of my past & future contributions to LibreOffice may be licensed under the MPLv2/LGPLv3+ dual license. - Maarten Hoes. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice

Cppcheck report password storage

irrecoverably, the password is still known. Perhaps that password should also be stored somewhere else, perhaps alongside the documents that describe what jobs run where, or somewhere else 'safe' ? Just my 2$. - Maarten Hoes. ___ LibreOffice mailing list

Re: CppCheck Report Update

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

Re: CppCheck Report Update

Ah. On Thu, Jun 23, 2016 at 6:37 PM, Maarten Hoes <hoes.maar...@gmail.com> wrote: > > B.) > drop sendEmail, install mail/mailx and install something like > sendmail/postfix/exim on vm140 and see if the cppcheck-report.sh script can > be modified to use mail/mailx instead.

Re: CppCheck Report Update

83/send-mail-through-gmail-using-perl On Sun, Jun 12, 2016 at 3:04 PM, Maarten Hoes <hoes.maar...@gmail.com> wrote: > Caolán McNamara wrote > > On Sun, 2016-02-28 at 01:35 +, > > > cppcheck.libreoffice@ > > > > >>> Note: > >>>

Re: CppCheck Report Update

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 >>>

Re: unit test failures (llvm/clang/scan-build/clang/clang++)

Hi, On Mon, Nov 23, 2015 at 10:02 AM, David Tardon wrote: > > The problem is: > > DynamicLibraryManagerException: "Failed to load dynamic library: > /home/maarten/src/libreoffice/core/workdir/LinkTarget/CppunitTest/libtest_sc_rangelst_test.so >

Re: unit test failures (llvm/clang/scan-build/clang/clang++)

On Mon, Nov 23, 2015 at 11:09 AM, Stephan Bergmann <sberg...@redhat.com> wrote: > > On 11/23/2015 11:02 AM, Maarten Hoes wrote: >> >> On Mon, Nov 23, 2015 at 10:51 AM, Stephan Bergmann <sberg...@redhat.com >> <mailto:sberg...@redhat.com>> wrote: >&g

Re: unit test failures (llvm/clang/scan-build/clang/clang++)

On Mon, Nov 23, 2015 at 11:25 AM, Stephan Bergmann <sberg...@redhat.com> wrote: > > On 11/23/2015 11:14 AM, Maarten Hoes wrote: >> >> On Mon, Nov 23, 2015 at 11:09 AM, Stephan Bergmann <sberg...@redhat.com >> <mailto:sberg...@redhat.com>> wrote: >&g

unit test failures (llvm/clang/scan-build/clang/clang++)

Hi, Im trying to run the llvm/clang static source code analyzer on libreoffice ~master, but ran into some unit test failures. I told 'scan-build' to use the clang/clang++ compilers instead of gcc. I ran the suggested 'make testname DEBUGCPPUNIT=TRUE' commands in order to get the backtraces of

Re: unit test failures (llvm/clang/scan-build/clang/clang++)

On Mon, Nov 23, 2015 at 10:12 AM, Maarten Hoes <hoes.maar...@gmail.com> wrote: > > Thanks. Would this be helpful ? > > > $ nm --dynamic /home/maarten/src/libreoffice/core/instdir/program/liborcus-0.10.so.0 | grep _ZNSt8ios_base7failureC2EPKcRKSt10error_code

Re: unit test failures (llvm/clang/scan-build/clang/clang++)

On Mon, Nov 23, 2015 at 10:51 AM, Stephan Bergmann <sberg...@redhat.com> wrote: > > On 11/23/2015 10:42 AM, Maarten Hoes wrote: >> >> On Mon, Nov 23, 2015 at 10:39 AM, Stephan Bergmann <sberg...@redhat.com >> > The Clang included in Fedora 23 is known to be bro

Re: unit test failures (llvm/clang/scan-build/clang/clang++)

On Mon, Nov 23, 2015 at 12:01 PM, Maarten Hoes <hoes.maar...@gmail.com> wrote: > > Or try doing something like 'make CXXFLAGS=-D_GLIBCXX_USE_CXX11_ABI=0' / 'CXXFLAGS=-D_GLIBCXX_USE_CXX11_ABI=0 ./autogen.sh' or even 'export CXXFLAGS=-D_GLIBCXX_USE_CXX11_ABI=0 && scan-build --

Re: unit test failures (llvm/clang/scan-build/clang/clang++)

Oh. Reading back my post, I notice the 'warning: the debug information found in "/usr/lib/debug//usr/lib64/libpcre.so.1.2.5.debug" does not match "/lib64/libpcre.so.1" (CRC mismatch)'. Upgrading/installing these took care of that : 'pcre-8.37-6.fc23.x86_64', 'pcre-debuginfo-8.37-6.fc23.x86_64'. No

Re: unit test failures (llvm/clang/scan-build/clang/clang++)

Hi, On Mon, Nov 23, 2015 at 10:39 AM, Stephan Bergmann <sberg...@redhat.com> wrote: > > On 11/23/2015 09:28 AM, Maarten Hoes wrote: >> >> Im trying to run the llvm/clang static source code analyzer on >> libreoffice ~master, but ran into some unit test failures.

Re: unit test failures (llvm/clang/scan-build/clang/clang++)

On Mon, Nov 23, 2015 at 10:42 AM, Maarten Hoes <hoes.maar...@gmail.com> wrote: > > Currently running: > > commit 55dd7c5223cc798d7b83559eba48b9d369db928a > Date: 2015-11-22 16:46:54 +0200 > Oh, and that would be : $ clang++ -v clang version 3.8.0 (trunk 253824) Target:

Re: unit test failures (llvm/clang/scan-build/clang/clang++)

On Mon, Nov 23, 2015 at 10:48 AM, Maarten Hoes <hoes.maar...@gmail.com> wrote: > > > > Currently running: > > > > commit 55dd7c5223cc798d7b83559eba48b9d369db928a > > Date: 2015-11-22 16:46:54 +0200 > > OOps. Wrong dir, wrong cmd. This is it: $ svn

Re: CppCheck configuration

Hi, On Sat, Sep 26, 2015 at 6:14 PM, Michaël Lefèvre wrote: > 1. there is a 'missingConfig' error, recommanding us to run the check with > --checkconfig > Im assuming you meant 'missingInclude' here, and not 'missingConfig' ? (I couldnt find a 'missingConfig'). If I

Re: CppCheck Report Update

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 ? :

CppCheck job failure (was CppCheck Report Update)

Hi, It seems this job is not running anymore for some weeks now. Was this intentional ? The host on which the job was scheduled (vm140.documentfoundation.org) appears to be down ? - Maarten -- View this message in context:

[Libreoffice-commits] dev-tools.git: cppcheck/cppcheck-report.sh

cppcheck/cppcheck-report.sh |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 0b9448dafce4b60291ce0526709586bf90faaf4b Author: Maarten Hoes hoes.maar...@gmail.com Date: Thu May 28 23:20:20 2015 +0200 Use XML v2. cppcheck doesnt report some issues with the legacy

[Libreoffice-commits] dev-tools.git: cppcheck/cppcheck-report.sh

cppcheck/cppcheck-report.sh | 21 - 1 file changed, 21 deletions(-) New commits: commit 4e7a671c5118c0076cd24e60d9d70389b21f181b Author: Maarten Hoes hoes.maar...@gmail.com Date: Sat May 2 12:33:37 2015 +0200 Remove unneeded set -xv lines. Change-Id

Re: CppCheck Report Update

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

Re: CppCheck Report Update

Hi, On Sun, Apr 26, 2015 at 10:26 PM, Maarten Hoes hoes.maar...@gmail.com wrote: Hi, On Sun, Apr 26, 2015 at 10:19 PM, Norbert Thiebaud nthieb...@gmail.com wrote: On Sun, Apr 26, 2015 at 3:00 PM, Maarten Hoes hoes.maar...@gmail.com wrote: On Sun, Apr 26, 2015 at 9:32 PM, Maarten

Re: CppCheck Report Update

Hi, On Sun, Apr 26, 2015 at 10:19 PM, Norbert Thiebaud nthieb...@gmail.com wrote: On Sun, Apr 26, 2015 at 3:00 PM, Maarten Hoes hoes.maar...@gmail.com wrote: On Sun, Apr 26, 2015 at 9:32 PM, Maarten Hoes hoes.maar...@gmail.com wrote: I cheated, and ran 'make -k check'. Oh

Re: CppCheck Report Update

On Sun, Apr 26, 2015 at 9:32 PM, Maarten Hoes hoes.maar...@gmail.com 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

Re: CppCheck Report Update

Hi, On Sun, Apr 26, 2015 at 9:26 PM, Norbert Thiebaud nthieb...@gmail.com 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,

Re: CppCheck Report Update

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:

Re: Application Hangs

Hi, Im not quite sure im the most qualified person to respond to this message, but ... Maybe having access to the document you are experiencing this issue would help. Also, you may want to sign up for and submit a bug report on: https://bugs.documentfoundation.org/ [ and add that document as

[Libreoffice-commits] buildbot.git: lcov-report/lcov-report.sh

lcov-report/lcov-report.sh |2 ++ 1 file changed, 2 insertions(+) New commits: commit 469be295be29c711874a144fc923936498471a5d Author: Maarten Hoes hoes.maar...@gmail.com Date: Wed Mar 4 20:51:40 2015 +0100 Allow for easier debugging by setting $DEBUG. Change-Id

[Libreoffice-commits] buildbot.git: lcov-report/lcov-report.sh

lcov-report/lcov-report.sh |2 ++ 1 file changed, 2 insertions(+) New commits: commit 1ba25afb4b0021f8d77f961ba4923fa27c390c62 Author: Maarten Hoes hoes.maar...@gmail.com Date: Wed Mar 4 21:14:19 2015 +0100 Also readlink -f BUILD_DIR when running BEFORE or AFTER. Change-Id

[Libreoffice-commits] buildbot.git: lcov-report/lcov-report.sh

lcov-report/lcov-report.sh |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) New commits: commit 7df6aedeed85fb726bebfac03e95838c80fce98c Author: Maarten Hoes hoes.maar...@gmail.com Date: Wed Mar 4 11:54:43 2015 +0100 Change report dir to have a fixed name. Change-Id

Re: LibreOffice support for MS-Visio Stencils/Templates and Shapes ?

Hi, I submitted an enhancement request for this in bugzilla: https://bugs.documentfoundation.org/show_bug.cgi?id=89469 - Maarten. ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice

Re: LibreOffice support for MS-Visio Stencils/Templates and Shapes ?

, 2015 at 10:43 AM, Maarten Hoes hoes.maar...@gmail.com wrote: Hi, I was wondering if LibreOffice (master) is currently supposed to have support for Microsoft Visio Stencils (.vss) and Templates (.vst) ? When I open one of these stencils in MS-Visio, I get a blank file onto which I can drag

Re: libreoffice build fails compiling with clang

On Mon, Feb 16, 2015 at 10:01 AM, Stephan Bergmann sberg...@redhat.com wrote: On 02/15/2015 12:46 PM, Maarten Hoes wrote: Im running into the build error listed below when I try to compile the LibreOffice master git repo with clang. Does anyone have an idea what might be going on, or how

libreoffice build fails compiling with clang

Hi, Im running into the build error listed below when I try to compile the LibreOffice master git repo with clang. Does anyone have an idea what might be going on, or how to go about troubleshooting the issue ? - Maarten [build CXX] sc/source/core/data/stlsheet.cxx [build CXX]

Re: Libreoffice 44 startet nicht mehr

Hi, 2015-02-15 20:36 GMT+01:00 Patrick Dreier patrick.dre...@gmx.net: Dear Sirs! Once I delete LibreOffice Quick Start will not start LibreOffice 4.4. Error The system can not find the file specified. With best regards! First off, I think you will find that stating your questions in the

Re: GSoC 2015

Hi, You should first start reading this page explaining how to be a good candidate for LibreOffice GSoC: https://wiki.documentfoundation.org/Development/GSoC/2015#How_to_apply - Maarten On Sat, Feb 14, 2015 at 8:00 AM, Sujeet IIITD sujeet14...@iiitd.ac.in wrote: Hello sir/mam myself Sujeet

[Libreoffice-commits] dev-tools.git: cppcheck/cppcheck-report.sh

cppcheck/cppcheck-report.sh |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) New commits: commit 3f1216fdaf3557521809df744a765d57900b2682 Author: Maarten Hoes hoes.maar...@gmail.com Date: Mon Feb 9 16:50:57 2015 +0100 Fix small typo in email message. Change-Id

[Libreoffice-commits] dev-tools.git: cppcheck/cppcheck-report.sh

cppcheck/cppcheck-report.sh | 16 ++-- 1 file changed, 14 insertions(+), 2 deletions(-) New commits: commit 9163b649f8b6b9262f84c7c098c0cf850770d0c5 Author: Maarten Hoes hoes.maar...@gmail.com Date: Sun Feb 8 07:52:52 2015 +0100 Improve note in email to include git location

Re: Aspiring applicant for gsoc 2015

Hi, This page has a section 'Getting Started with Development', where a few suggestions are made on how and where to get started. https://wiki.documentfoundation.org/Development - Maarten ___ LibreOffice mailing list

[Libreoffice-commits] dev-tools.git: cppcheck/cppcheck-report.sh

cppcheck/cppcheck-report.sh |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) New commits: commit 755c011e790d4083c37793778b3364d50b513955 Author: Maarten Hoes hoes.maar...@gmail.com Date: Mon Feb 2 14:23:31 2015 +0100 Set default for 'CPPCHECK_DIR' to something slightly more

Cppcheck report failure automatic notification email

Hi, Currently a cron job is scheduled to generate cppcheck reports on the LibreOffice code once a week. On a successful run, an automatic notification email is send to the developer list, containing an url to the latest report. But as I may not be around forever, Im trying to figure out who

[Libreoffice-commits] buildbot.git: lcov-report/lcov-report.sh lcov-report/README lcov-report/tinderbox

files changed, 8 insertions(+), 6 deletions(-) New commits: commit 45c3803ace2a9e17bae6f5d537bc29df81c8af0e Author: Maarten Hoes hoes.maar...@gmail.com Date: Mon Jan 26 12:54:08 2015 +0100 Added 'gb_GCOV=YES' to make commands. Change-Id: I88f43377c4614e14d4cc34aace0c8b2e3544a302

Re: CppCheck Report Failure

Hi, Thanks for your feedback. The error had to do with the different way the language environment variables get set when run from a login shell and from cron. Setting them (LANG=, LC_*=) explicitly to something UTF-8 in the script resolves the issue.

[Libreoffice-commits] dev-tools.git: cppcheck/cppcheck-report.sh

cppcheck/cppcheck-report.sh | 17 - 1 file changed, 16 insertions(+), 1 deletion(-) New commits: commit d7c8e6f5c3993dd3bea2dce1e983c7259f8db7c6 Author: Maarten Hoes hoes.maar...@gmail.com Date: Mon Jan 26 09:09:10 2015 +0100 set LANG and LC_* to fix 'UnicodeEncodeError

Re: CppCheck Report Failure

Hi, On Mon, Jan 26, 2015 at 10:22 AM, Miklos Vajna vmik...@collabora.co.uk wrote: On Sun, Jan 25, 2015 at 01:08:29AM +, cppcheck.libreoff...@gmail.com cppcheck.libreoff...@gmail.com wrote: The cppcheck job failed with message: Failed to run cppcheck-htmlreport. This job was run at

Re: buildbot/bin/sendEmail issue

Hi, On Mon, Jan 26, 2015 at 6:34 AM, Jonathan Aquilina eagles051...@gmail.com wrote: Hi Maarten, Did you manage to get it working? Yes, after patching sendEmail. Thanks, - Maarten ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org

[Libreoffice-commits] dev-tools.git: cppcheck/cppcheck-report.sh

cppcheck/cppcheck-report.sh | 18 ++ 1 file changed, 10 insertions(+), 8 deletions(-) New commits: commit a71cf8c84898db994215d3a822027e0d58dad080 Author: Maarten Hoes hoes.maar...@gmail.com Date: Sun Jan 25 10:08:09 2015 +0100 Fix 'UnicodeEncodeError'. Get correct git

[Libreoffice-commits] buildbot.git: bin/sendEmail

bin/sendEmail |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit b855d0a95e74b6ab04d5e5e714ebbfebb7881c31 Author: Maarten Hoes hoes.maar...@gmail.com Date: Sat Jan 24 10:57:52 2015 +0100 Work around 'invalid SSL_version' error. Change-Id

buildbot/bin/sendEmail issue

Hi, In an attempt to send email from a unix shell script, im trying to use the buildbot/bin/sendEmail command. This seems like a better choice than just using 'mailx' from some vm's commandline, as it would allow for logging into an smtp server with gmail/google credentials, allowing for sending

Re: buildbot/bin/sendEmail issue

Hi, On Sat, Jan 24, 2015 at 10:52 AM, Matúš Kukan matus.ku...@gmail.com wrote: On 24 January 2015 at 10:38, Maarten Hoes hoes.maar...@gmail.com wrote: if ($conf{'tls_server'} == 1 and $conf{'tls_client'} == 1 and $opt{'tls'} =~ /^(yes|auto)$/) { printmsg(DEBUG = Starting TLS

Re: buildbot/bin/sendEmail issue

Hrm. I did some googling, and it seems I am not the only one running into this issue. It seems making this change in the script can be used as a workaround, but im not sure if this is seen as an acceptable change. $ diff -u ./buildbot/bin/sendEmail ~/tmp/sendEmail --- ./buildbot/bin/sendEmail

[Libreoffice-commits] dev-tools.git: cppcheck/cppcheck-report.sh

cppcheck/cppcheck-report.sh | 75 ++-- 1 file changed, 46 insertions(+), 29 deletions(-) New commits: commit 09c674747d7b8afff7963577787f01fc16fdd27b Author: Maarten Hoes hoes.maar...@gmail.com Date: Sat Jan 24 14:17:02 2015 +0100 Replace usage

[Libreoffice-commits] dev-tools.git: cppcheck/cppcheck-report.sh

cppcheck/cppcheck-report.sh | 65 +++- 1 file changed, 58 insertions(+), 7 deletions(-) New commits: commit ec1c1ddcc8eb03b71e8e69c5c2644a4d80947730 Author: Maarten Hoes hoes.maar...@gmail.com Date: Wed Jan 21 14:13:11 2015 +0100 redirect output

[Libreoffice-commits] dev-tools.git: cppcheck/cppcheck-report.sh

cppcheck/cppcheck-report.sh | 179 1 file changed, 179 insertions(+) New commits: commit 64ae2aa598fadfe55746724dde96fc561573e843 Author: Maarten Hoes hoes.maar...@gmail.com Date: Mon Jan 19 14:01:03 2015 +0100 Added automated cppcheck

[Libreoffice-commits] dev-tools.git: cppcheck/cppcheck-report.sh

cppcheck/cppcheck-report.sh |1 + 1 file changed, 1 insertion(+) New commits: commit 52626df964a70fbdfb485f189814d072c1ae4631 Author: Maarten Hoes hoes.maar...@gmail.com Date: Mon Jan 19 19:09:01 2015 +0100 Added creation of UPLOAD_DIR. Change-Id

  1   2   >