Thanks for pinging.
I had a 2nd fresh (post vacations) look at your logs. There are many anomalies even though I cannot directly link them to the fact that there are no LoCs found in the Omada.ODW.Logging directory.
Here are those anomalies:
2020-06-11T15:18:24.4595394Z WARN: Exception caught during execution of command '[git, config, --system, --edit]' in 'F:\agent4\externals\git\cmd', return code '129', error message 'error: only one config file at a time
This is likely to break git integration, and this is further reinforced by other messages downstream as below:
2020-06-11T15:37:12.7455735Z WARN: Missing blame information for the following files:
2020-06-11T15:37:12.7462471Z WARN: ... Plenty of files listed ...
It would be good to understand why these warnings, that however would not immediately justify why the Omada.ODW.Logging directory has no LoCs.
The next more worrying log is:
2020-06-11T15:19:32.8098395Z INFO: ------------- Run sensors on module Omada.ODW.Logging
2020-06-11T15:19:34.5648478Z WARN: No Roslyn issues report found for this project.
This clearly means that this module is not properly analyzed (like Omada.ODW.Logging.2014, Omada.ODW.Logging.2017 by the way).
After this I noticed that the 3 above “modules” are actually pointing to the same directory (
src\ODW\Utilities\Omada.ODW.Logging). This could well be the root cause of the problem.
Can you explain how you project is structure so that, as part of your solution, several projects link to the same physical directory ?
Would it be possible to run a test with a single instance of the Omada.ODW.Logging module in the solution ?