question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Tests are failing with merge mismatch

See original GitHub issue

Before you file an issue, please check the README.md’s known issues section.

Describe the bug (A clear and concise description of what the bug is.) When running test (sometimes even after scanning) the tests are marked as failing with the following error profiling: /external/googletest/googletest/CMakeFiles/gtest.dir/src/gtest-all.cc.gcda: Merge mismatch for function 1

To Reproduce (Steps to reproduce the behavior:)

  1. Go to ‘…’
  2. Click on ‘…’
  3. Scroll down to ‘…’
  4. See error

Expected behavior (A clear and concise description of what you expected to happen.)

Screenshots (If applicable, add screenshots to help explain your problem.)

Desktop (please complete the following information):

  • Extension Version [e.g. 22] 2.6.4
  • VS Code Version [e.g. 22] 1.36.1
  • Catch2/Google Test Version 1.8
  • OS Type and Version Win 10

Log (Attach log. (optional, Set: catch2TestExplorer.logfile and reproduce the bug.) Warning: Log probably contains file and test names too.)

Additional context Add any other context about the problem here.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:29 (13 by maintainers)

github_iconTop GitHub Comments

2reactions
matepekcommented, Aug 2, 2019

A modified build will be released soon. If that is the problem, it should be solved.

1reaction
NINI1988commented, Aug 1, 2019

I have a similar issue while using code coverage gcc --coverage.

Everything works fine until i set: “catch2TestExplorer.workerMaxNumber”: 2,

I guess it happens when multiple test application run in parallel and modifying the same coverage files?

profiling:D:\test3\cLogTest/Log.gcda:Data file mismatch - some data files may have been concurrently updated without locking support
Read more comments on GitHub >

github_iconTop Results From Across the Web

Tests on GCOV build fail with Merge mismatch for function
Something in the code that is being exercised by those 3 tests seems to be incompatible with the code generated or linked by...
Read more >
ci: gcov: "merge mismatch" errors · Issue #10332 - GitHub
This issue is meant to track "merge mismatch" errors due to using gcov ... use stdio channel: FAIL test/functional/helpers.lua:113: Expected ...
Read more >
gcov warning: merge mismatch for summaries - Stack Overflow
This happens when one of the objects you're linking into an executable changes significantly. For example it gains or loses some lines of ......
Read more >
Coverage merge failures cause test_process_slow stderr ...
When tor's coverage CI fails to merge coverage records, it logs to stderr. This causes the process stderr checks to fail.
Read more >
Re-executing failed test cases and merging outputs with ...
Re-executing failed tests (–rerunfailed) appeared in Robot Framework 2.8. And since version 2.8.4 a new option (–merge) was added to rebot ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found