Re: Error generating coverage report

Hi Peter,

On 12/12/17 3:20 PM, Peter Eisentraut wrote:
>>
>> make: Entering directory `/home/vagrant/test/build/src/bin/pg_basebackup'
>> /usr/bin/lcov --gcov-tool /usr/bin/gcov -q --no-external -c -i -d . -d
>> /postgres/src/bin/pg_basebackup -o lcov_base.info
>> geninfo: ERROR: no .gcno files found in /postgres/src/bin/pg_basebackup!
>> make: *** [lcov_base.info] Error 255
>> make: *** Deleting file `lcov_base.info'
>> make: Leaving directory `/home/vagrant/test/build/src/bin/pg_basebackup'
>
> The -d options should accumulate, so that it should look in both places.
>
> Wild guess: If the /postgres directory is some kind of vboxsf mount,
> there might be problems if symlinks are involved.

/postgres is a vboxsf mount. However, I copied /postgres to
/home/vagrant/src and still see the same error:

$ make -C test/build/src/bin/pg_basebackup coverage-html
make: Entering directory `/home/vagrant/test/build/src/bin/pg_basebackup'
/usr/bin/lcov --gcov-tool /usr/bin/gcov -q --no-external -c -i -d . -d
/home/vagrant/src/src/bin/pg_basebackup -o lcov_base.info
geninfo: ERROR: no .gcno files found in
/home/vagrant/src/src/bin/pg_basebackup!
make: *** [lcov_base.info] Error 255
make: *** Deleting file `lcov_base.info'
make: Leaving directory `/home/vagrant/test/build/src/bin/pg_basebackup'

Thoughts?

--
-David
david(at)pgmasters(dot)net