Investigate "warning: N functions have mismatched data" warning from llvm-cov" |
|||||||
Issue descriptionThat happened when I was generating coverage report for 35 unit test binaries: $ tools/code_coverage/coverage.py courgette_unittests gpu_unittests headless_unittests audio_unittests media_unittests media_blink_unittests media_mojo_unittests media_service_unittests net_unittests services_unittests service_manager_unittests skia_unittests storage_unittests blink_heap_unittests wtf_unittests blink_common_unittests angle_unittests pdfium_unittests accessibility_unittests gfx_unittests gl_unittests keyboard_unittests snapshot_unittests views_unittests wm_unittests url_unittests breakpad_unittests content_unittests mojo_common_unittests sql_unittests unit_tests cc_blink_unittests crypto_unittests pdf_unittests swiftshader_unittests \ > -b out/coverage \ > -o total_report \ > -c 'out/coverage/courgette_unittests' \ > -c 'out/coverage/gpu_unittests' \ > -c 'out/coverage/headless_unittests' \ > -c 'out/coverage/audio_unittests' \ > -c 'out/coverage/media_unittests' \ > -c 'out/coverage/media_blink_unittests' \ > -c 'out/coverage/media_mojo_unittests' \ > -c 'out/coverage/media_service_unittests' \ > -c 'out/coverage/net_unittests' \ > -c 'out/coverage/services_unittests' \ > -c 'out/coverage/service_manager_unittests' \ > -c 'out/coverage/skia_unittests' \ > -c 'out/coverage/storage_unittests' \ > -c 'out/coverage/blink_heap_unittests' \ > -c 'out/coverage/wtf_unittests' \ > -c 'out/coverage/blink_common_unittests' \ > -c 'out/coverage/angle_unittests' \ > -c 'out/coverage/pdfium_unittests' \ > -c 'out/coverage/accessibility_unittests' \ > -c 'out/coverage/gfx_unittests' \ > -c 'out/coverage/gl_unittests' \ > -c 'out/coverage/keyboard_unittests' \ > -c 'out/coverage/snapshot_unittests' \ > -c 'out/coverage/views_unittests' \ > -c 'out/coverage/wm_unittests' \ > -c 'out/coverage/url_unittests' \ > -c 'out/coverage/breakpad_unittests' \ > -c 'out/coverage/content_unittests' \ > -c 'out/coverage/mojo_common_unittests' \ > -c 'out/coverage/sql_unittests' \ > -c 'out/coverage/unit_tests' \ > -c 'out/coverage/cc_blink_unittests' \ > -c 'out/coverage/crypto_unittests' \ > -c 'out/coverage/pdf_unittests' \ > -c 'out/coverage/swiftshader_unittests'
,
Apr 2 2018
I suspect that this is a duplicate of issue 801364 , just another error message accumulating individual errors.
,
Apr 27 2018
I'm still seeing a few of these during reports generation, so we'll have to take a look later. + tools/code_coverage/coverage.py chrome <test_binaries> <fuzzer_binaries> -b out/coverage -o 554161 [2018-04-27 07:29:11,578] Generating code coverage report in html (this can take a while depending on size of target!) warning: 43 functions have mismatched data warning: 43 functions have mismatched data [2018-04-27 09:59:36,804] Index file for html report is generated as: file:///mnt/ram-disk/chromium/src/554161/index.html + tools/code_coverage/coverage.py <test_binaries> -b out/coverage -o 554161_tests_only [2018-04-27 09:59:37,707] Generating code coverage report in html (this can take a while depending on size of target!) warning: 12 functions have mismatched data warning: 12 functions have mismatched data [2018-04-27 12:10:36,689] Index file for html report is generated as: file:///mnt/ram-disk/chromium/src/554161_tests_only/index.html + tools/code_coverage/coverage.py <fuzzer_binaries> -b out/coverage -o 554161_fuzzers_only [2018-04-27 12:10:37,124] Generating code coverage report in html (this can take a while depending on size of target!) warning: 1 functions have mismatched data warning: 1 functions have mismatched data [2018-04-27 13:08:06,083] Index file for html report is generated as: file:///mnt/ram-disk/chromium/src/554161_fuzzers_only/index.html
,
May 11 2018
,
May 11 2018
,
Jan 3
This is not a blocker and have not caused any noticeable issues, but might be good to explore and understand where these warnings are coming from. If I were to debug this, I'd probably add some printf()s to llvm-cov code to print out function and file names when a mismatch happens. It's quite weird that there is a mismatch at the report generation step, as it means that .profdata / binary / source code do not match each other. Assigning to Yuke for further triage.
,
Jan 3
,
Jan 11
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by mmoroz@chromium.org
, Jan 12 2018Status: Available (was: Untriaged)