On 26.11.2012 19:56, Julian Foad wrote:
> Stefan Fuhrmann wrote:
>
>> I was wondering whether we could have one or two of
>> our UNIX build bots create a code coverage profile
>> and make the results available online.
>>
>> Here is what I use in my test runner script:
>>
>> [[[
>> env CFLAGS='-fprofile-arcs -ftest-coverage' ./configure \
>> --disable-shared --enable-maintainer-mode $moreopts
>>
>> make -sj 2> /dev/null > /dev/null
>> make svnserveautocheck PARALLEL=1
>
> Some of the Python tests error out when I run them in parallel like this. The errors are:
> [[[
> W: profiling:/.../subversion/libsvn_subr/.libs/nls.gcda:Invocation mismatch - some data files may have been removed
> ]]]
>
> I found an email <http://gcc.gnu.org/ml/gcc-help/2005-11/msg00074.html> which says "gcov instrumentation is multi-process safe, but not multi-thread safe. The
> multi-processing safety relies on OS level file locking, which is not available
> on some systems.".
Maybe we should replace threading with multiprocess to run parallel
python tests. They'd block less in the GIL as well.
-- Brane
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Received on 2012-11-26 20:10:51 CET