Task #3386
closedMove code coverage check to Ubuntu 14.04
100%
Description
Per NDN platform policy, Ubuntu 12.04 support would be discontinued upon Ubuntu 16.04 release.
In preparation for that, code coverage check should be moved to Ubuntu 14.04.
This task includes:
- On Ubuntu 14.04, verify the build script with code coverage turned on works correct, and the code coverage report is as accurate as what's generated on Ubuntu 12.04.
- Modify Jenkins configuration to run code coverage checks on Ubuntu 14.04.
- Add more Ubuntu 14.04 slaves, if needed.
- Retire excessive Ubuntu 12.04 slaves.
Files
Updated by Junxiao Shi almost 9 years ago
- Description updated (diff)
- Due date set to 03/21/2016
- Estimated time set to 3.00 h
Ubuntu 16.04 will be released on Apr 21, 2016. This task should be completed one month before that.
Updated by Junxiao Shi almost 9 years ago
- Assignee set to Eric Newberry
20160316 call decides to assign this to Eric.
Updated by Eric Newberry almost 9 years ago
- Status changed from New to In Progress
Updated by Eric Newberry almost 9 years ago
I tested the code coverage for ndn-atmos, ndn-cxx, ndns, and NFD. The only change that was necessary to get it working was to install gcovr from python pip instead of apt-get.
Updated by Davide Pesavento almost 9 years ago
Why is that needed? The packaged gcovr is too old?
Updated by Eric Newberry almost 9 years ago
Davide Pesavento wrote:
Why is that needed? The packaged gcovr is too old?
Yes, that appears to be the reason. The version packed with Ubuntu 14.04 (gcovr 2.4) encounters problems parsing the output of gcc 4.8. The version from pip (gcovr 3.2) looks like it works.
Updated by Eric Newberry over 8 years ago
- File ndn-atmos-coverage-1204.html ndn-atmos-coverage-1204.html added
- File ndn-atmos-coverage-1404.html ndn-atmos-coverage-1404.html added
- File ndn-cxx-coverage-1204.html ndn-cxx-coverage-1204.html added
- File ndn-cxx-coverage-1404.html ndn-cxx-coverage-1404.html added
- File ndns-coverage-1204.html ndns-coverage-1204.html added
- File ndns-coverage-1404.html ndns-coverage-1404.html added
- File NFD-coverage-1204.html NFD-coverage-1204.html added
- File NFD-coverage-1404.html NFD-coverage-1404.html added
Here are coverage reports generated for ndn-atmos, ndn-cxx, ndns, and NFD on 12.04 and 14.04.
Updated by Junxiao Shi over 8 years ago
Reply to note-7:
Do you see major difference between a report on 12.04 and a report on 14.04?
If yes, point out the difference and ask project owner to have a look.
If not, proceed with changing the configuration on production Jenkins.
Updated by Davide Pesavento over 8 years ago
I checked ndn-cxx and NFD. The new reports look ok to me. There are some differences, but I don't think we should waste time investigating them.
Updated by Eric Newberry over 8 years ago
- % Done changed from 0 to 90
Davide Pesavento wrote:
I checked ndn-cxx and NFD. The new reports look ok to me. There are some differences, but I don't think we should waste time investigating them.
The differences in ndns and ndn-atmos look similar to the differences in ndn-cxx and NFD, so I'll prepare the nodes for the switch.
Updated by Eric Newberry over 8 years ago
Code coverage labels have been moved to 64-bit 14.04 nodes. I'm waiting for the release of 16.04 before retiring the 12.04 nodes.
Updated by Junxiao Shi over 8 years ago
Reply to note-11:
Add more Ubuntu 14.04 slaves, if needed.
Are there sufficient slaves to run two builds at the same time?
This means four 14.04 slaves.
Retire excessive Ubuntu 12.04 slaves.
We only need two 12.04 slaves.
Anything more than that can be retired now.
Updated by Eric Newberry over 8 years ago
Junxiao Shi wrote:
We only need two 12.04 slaves.
Anything more than that can be retired now.
Two of the four 12.04 nodes have been retired.
Updated by Eric Newberry over 8 years ago
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
Updated by Junxiao Shi over 8 years ago
- Blocks Task #3599: Drop build support for Ubuntu 12.04 added
Updated by Davide Pesavento over 8 years ago
- Status changed from Resolved to Closed
I suppose we can close this.