NFD

One related problem is that, the report shows only .hpp files, and does not show .cpp files.

I suspect gcovr is not generating the right report. I will need to dive deeper on this issue. Unfortunately I am not available until Monday 8/25. If this is not very urgent I'll continue to look at this issue on 8/25.

This is not urgent. Work on it whenever you have time.

Is there any progress on this? This is necessary to improve code coverage.

Not yet I was working on cross compiling NFD on android devices these days.

Is there any progress on this? This is necessary to improve code coverage.

The basic problem that I discovered was that the coverage command (gcovr) should run from the same directory as the compiler. In our case, all compilation happens inside build/ folder. The result of not running gcovr being in build/ folder prevents finding .cpp files (names of the files gcov was looking for was like ../daemon/xxx).

I have fixed the command on jenkins, adding additional filters to analyze only daemon/, core/, and rib/ folders. Previously our report was also incorrectly showing websocketpp, tools and other folders with source files.

The bug fix is incomplete.

Although .cpp files are listed in the report, all files in the report still show "Source code is unavailable. Some possible reasons are:".

I haven't fixed things with ndn-cxx repo, but there are currently no problems with NFD reports. I can see source code for hpp and cpp files... Can you give example where it's not working?

This shows me content of fib.hpp and hightlights some lines, though I don't have much clue what is the logic for this highlighting.

Apparently, the plugin has some strange retention policy for source code. It claims that it has code only for the most recent build.

I just observed code "disappear" while the most recent build fail. The code reappear after I retried the job.

As of Oct 08 01:13 UTC, the latest build of NFD is build 1689 and is successful, however daemon/table/cs.cpp does not have source code.

Please change retention policy to: retain the last 5 successful builds for each project.