Coverage broken

[BridgeAR]

https://coverage.nodejs.org/ displays nothing new since nine days. I feel something has gone wrong here?

/cc @mhdawson

[targos]

Last run: https://ci.nodejs.org/view/All/job/node-test-commit-linux-coverage/542/

if [ ! -f gcovr/scripts/gcovr.orig ]; then \
		(cd gcovr && patch -N -p1 < \
		"/home/iojs/build/workspace/node-test-commit-linux-coverage/nodes/benchmark/build/jenkins/scripts/coverage/gcovr-patches.diff"); fi
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/scripts/gcovr b/scripts/gcovr
|index 034779c86d29..e68b239c424f 100755
|--- a/scripts/gcovr
|+++ b/scripts/gcovr
--------------------------
File to patch: 
Skip this patch? [y] 
Skipping patch.
2 out of 2 hunks ignored
make: *** [coverage-build] Error 1
Build step 'Execute shell' marked build as failure

The gcovr script moved: gcovr/gcovr@27756c8

[killagu]

Update gcovr-patches.diff can fix it,I will raise a PR in nodejs/build to fix it.
Makefile should be updated too.

[trivikr]

FYI https://coverage.nodejs.org/ doesn't show any past coverages now.

[BridgeAR]

Nice that this got fixed. @mhdawson would you please have a look at the concrete coverage output from today e.g. https://coverage.nodejs.org/coverage-ee34d7e54ae39766/index.html? Is this going to be fixed with the next regular coverage run?