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.
Failed to retrieve coverage info for ...
See original GitHub issueDuring the execution of stryker this error appears intermittently: “Failed to retrieve coverage info for <test method>”
Logs
Original project: https://github.com/sergiocabral/Cabrones.Kli
Output log:
C:\Git\Kli\Test.Kli (master -> github)
λ dotnet stryker
_____ _ _ _ _ ______ _______
/ ____| | | | | \ | | ____|__ __|
| (___ | |_ _ __ _ _| | _____ _ __ | \| | |__ | |
\___ \| __| '__| | | | |/ / _ \ '__| | . ` | __| | |
____) | |_| | | |_| | < __/ | | |\ | |____ | |
|_____/ \__|_| \__, |_|\_\___|_| (_)|_| \_|______| |_|
__/ |
|___/
Version: 0.14.0 (beta)
[16:37:33 INF] The project C:\Git\Kli\Kli\Kli.csproj will be mutated
[16:37:34 INF] Started initial build using dotnet build
[16:37:37 INF] Initial build successful
[16:38:00 INF] Using testrunner VsTest
[16:38:00 INF] Total number of tests found: 371
[16:38:00 INF] Initial testrun started
[16:38:03 INF] Using 9617 ms as testrun timeout
[16:38:06 INF] 2 mutants got status CompileError. Reason: Could not compile
[16:38:06 INF] 138 mutants ready for test
[16:38:06 INF] Capture mutant coverage using 'perTest' mode.
[16:38:18 WRN] Failed to retrieve coverage info for Kli.Input.TestIInput.verifica_se_os_métodos_existem_com_base_na_assinatura.
[16:38:18 WRN] Failed to retrieve coverage info for Kli.Input.TestIInput.verifica_se_os_métodos_existem_com_base_na_assinatura.
[16:38:18 WRN] Failed to retrieve coverage info for Kli.Input.TestIInput.verifica_se_os_métodos_existem_com_base_na_assinatura.
[16:38:18 WRN] Failed to retrieve coverage info for Kli.Input.TestIInput.verifica_se_o_total_de_métodos_públicos_declarados_está_correto_neste_tipo.
[16:38:18 WRN] Failed to retrieve coverage info for Kli.i18n.TestITranslate.verifica_se_os_métodos_existem_com_base_na_assinatura.
[16:38:18 WRN] Failed to retrieve coverage info for Kli.i18n.TestITranslate.verifica_se_os_métodos_existem_com_base_na_assinatura.
[16:38:18 WRN] Failed to retrieve coverage info for Kli.i18n.TestITranslate.verifica_se_os_métodos_existem_com_base_na_assinatura.
[16:38:18 WRN] Failed to retrieve coverage info for Kli.i18n.TestITranslate.verifica_se_os_métodos_existem_com_base_na_assinatura.
[16:38:18 WRN] Failed to retrieve coverage info for Kli.i18n.TestITranslate.verifica_se_os_métodos_existem_com_base_na_assinatura.
[16:38:18 WRN] Failed to retrieve coverage info for Kli.i18n.TestITranslate.verifica_se_os_métodos_existem_com_base_na_assinatura.
[16:38:18 WRN] Failed to retrieve coverage info for Kli.i18n.TestITranslate.verifica_se_os_métodos_existem_com_base_na_assinatura.
[16:38:18 WRN] Failed to retrieve coverage info for Kli.i18n.TestITranslate.verifica_se_os_métodos_existem_com_base_na_assinatura.
[16:38:18 WRN] Failed to retrieve coverage info for Kli.i18n.TestITranslate.verifica_se_o_total_de_métodos_públicos_declarados_está_correto_neste_tipo.
[16:38:18 INF] Congratulations, all mutants are covered by tests!
[16:38:18 INF] Coverage analysis eliminated 93,52% of tests (i.e. 47879 tests out of 51198).
Testing mutant | ██████████ | 138 / 138 | 100 % | ~0m 00s |
Killed : 125
Survived: 7
Timeout : 6
Expected behavior This error should not appear, or at least indicate how to be resolved. Or, do not change the output result with each execution.
Desktop (please complete the following information):
- OS: Windows 10
- Type of project: NET Core, Console Application
- Framework Version: netcoreapp3.0
- Stryker Version 0.14.0 (beta)
Additional context N/A
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Error: could not find coverage info for source files #394
I'm trying to set up Code climate for my app and I keep getting this error on CircleCI. package.json snippet "name": "dista", ...
Read more >Test Coverage Troubleshooting Tips
The reporter is unable to find your repo's test reporter ID. This value either needs to configured within the environment or passed directly...
Read more >ERROR while code coverage report using lcov
I ran into a similiar problem where lcov also failed to write the file. ... lcov -a $(abspath test_fast_cxxtest_gcov__base.info) \ -a ...
Read more >No coverage information will be saved because all LCOV files ...
No coverage information will be saved because all LCOV files cannot be found for my javascript project using Github actions.
Read more >Not able to generate ".coverage" report while running code ...
I'm trying to run code coverage testing from command line using below commands: vstest.console.exe CoverTest.dll /EnableCodeCoverage ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think this message can safely be ignored here. It signals that the test coverage mechanism failed to report its results when requested. It may be related some internal error, but it also happens if the test coverage mechanism is not started (yet).
And the capture mechanism starts when the first mutant is tested. I took a look at the tests for this project and al the ones listed above do not call any actual code, so they don’t cover any mutant.
The randomness of this is (probably) due to VsTest ordering logic.
This message should only be reported as an issue when the test actually covers some mutant.
PR #936 eliminates this message for most circumstances. Coverage capture is now considered as reliable.