kcov: error: ${LINENO} is not an integer

[jakub-bochenski]

I'm trying to use kcov with bats, it seems to produce a coverage report, but the output has an error message before each test, e.g.

$ kcov/usr/local/bin/kcov out/coverage support/bats/bin/bats test/helpers/
1..20
kcov: error: ${LINENO} is not an integer
ok 1 is_uuid returns true for valid UUID

Weirdly at one point it prints out the trace of internal code of bats-assert/assert_equal:

  line2
  line3 != \l\i\n\e\1\
\ \ \l\i\n\e\2\
\ \ \l\i\n\e\3 ]]

I'm using https://github.com/SimonKagstrom/kcov/releases/download/v40/kcov-amd64.tar.gz

[jakub-bochenski]

https://github.com/SimonKagstrom/kcov/releases/download/v42/kcov-amd64.tar.gz is the same

[jakub-bochenski]

Same with docker, but now it prints the errors first before all tests:

$ docker run --rm   -v "$PWD":/src   -w /src kcov/kcov:latest   /usr/local/bin/kcov     --include-path=script out/coverage support/bats/bin/bats test/helpers
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
  line2
  line3 != \l\i\n\e\1\
\ \ \l\i\n\e\2\
\ \ \l\i\n\e\3 ]]
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
kcov: error: ${LINENO} is not an integer
1..20
ok 1 is_uuid returns true for valid UUID

[jakub-bochenski]

In addition if the bats test suite has a setup_suite file it seems to enable bash trace output:

1..37
+ set -eET
+ flags=('--dummy-flag')
+ num_jobs=1
+ extended_syntax=
+ BATS_TRACE_LEVEL=0
+ declare -r BATS_RETRY_RETURN_CODE=126
+ export BATS_TEST_RETRIES=0
+ BATS_TEST_RETRIES=0
+ [[ 5 -ne 0 ]]
+ case "$1" in
+ shift
+ [[ 4 -ne 0 ]]
+ case "$1" in
+ flags+=('-T')
+ shift
+ [[ 3 -ne 0 ]]
+ case "$1" in
+ break
+ export BATS_TEST_FILE_NUMBER=1
<lots of trace lines>

[jakub-bochenski]

Looking at the CI setup of bats-core itself: they don't get the LINENO errors, but they do get the extra output

E.g. https://github.com/bats-core/bats-core/actions/runs/15121858161/job/42505838976 vs https://github.com/bats-core/bats-core/actions/runs/15121858161/job/42505838916

ok 328 junit formatter as report formatter creates report.xml
hello Bilbo ]]
hello Bilbo
teardown FD3 ]]
hello Bilbo
teardown FD3 ]]
hello Bilbo
teardown FD3 =~ �\[[0-9;]+m ]]
hello Bilbo ]]
  `false' failed ]]
  `false' failed
# setup stdout ]]
  `false' failed
# setup stdout
# hello stdout ]]
hello Bilbo
teardown FD3 ]]
hello Bilbo
teardown FD3 =~ �\[[0-9;]+m ]]
  `false' failed
# setup stdout
# hello stdout
# teardown stdout ]]
  `false' failed
# setup stdout
# hello stdout
# teardown stdout =~ �\[[0-9;]+m ]]

ok 329 junit does not mark tests with FD 3 output as failed (issue #360)

vs

ok 329 junit formatter as report formatter creates report.xml
ok 330 junit does not mark tests with FD 3 output as failed (issue #360)

[jakub-bochenski]

i guess the extra output was already reported as #464