I followed the steps to calculate coverage on my own checkout, and linking the binary seems to take forever. I've been linking for a couple hours - not much cpu or ram usage by the linker, so I'm not sure what is happening here.
CL:
python tools/code_coverage/coverage.py content_unittests -b out/coverage -o out/report -c 'out/coverage/content_unittests --gtest_filter=SessionStorageContextMojo*' -f content/browser/dom_storage/
[2018-06-18 14:03:12,529 INFO] Building ['content_unittests'].
ninja: Entering directory `/usr/local/google/home/dmurph/cr-home/src/out/coverage'
[8/9] LINK ./content_unittests
Comment 1 by dmu...@chromium.org
, Jun 18 2018