8000 Excessive "No block number defined, assuming 0" messages · Issue #989 · gcovr/gcovr · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Excessive "No block number defined, assuming 0" messages #989

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Syeberman opened this issue Oct 12, 2024 · 1 comment · Fixed by #990
Closed

Excessive "No block number defined, assuming 0" messages #989

Syeberman opened this issue Oct 12, 2024 · 1 comment · Fixed by #990

Comments

@Syeberman
Copy link

Describe the bug

In gcovr 8.0, the following string is being printed thousands of times:

(INFO) No block number defined, assuming 0

This print was added in #976.

To Reproduce

.venv/bin/gcovr --lcov coverage.codecov/munit_test.lcov --use-gcov-files coverage.codecov/munit_test.gcov/ --gcov-ignore-parse-errors

I am unsure what causes the block number to be undefined in .gcov files. I will check my project (nohtyP) to see if there's a gcov option I'm missing.

Expected behavior

I would recommend removing this print, or printing once rather than at every applicable line.

Screenshots

From my build https://ci.appveyor.com/project/Syeberman/nohtyp/builds/50783482?fullLog=true:

image

Relevant files:

Desktop (please complete the following information)

  • OS: Ubuntu 22.04
  • GCC version: GCC 11, 13
  • GCOVR version: 8.0
  • Project directory layout:
    • Project: nohtyP
    • ./Build/make coverage creates a Build/native/coverage/munit_test.gcov.tar.gz file containing the .gcov files
@Spacetown
Copy link
Member

This behaviour was discussed in #973 because gvoc is missing this info for some functions. It seems that the "some" is many for you.
I'll change it to be printed only once.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants
0