-
Notifications
You must be signed in to change notification settings - Fork 29.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Coverage broken #18938
Comments
Last run: https://ci.nodejs.org/view/All/job/node-test-commit-linux-coverage/542/
The gcovr script moved: gcovr/gcovr@27756c8 |
Update |
PR-URL: #1145 Ref: nodejs/node#18938 Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: MichaëZasso <targos@protonmail.com>
FYI https://coverage.nodejs.org/ doesn't show any past coverages now. |
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? |
PR-URL: nodejs#18958 Fixes: nodejs#18938 Ref: nodejs/build#1145 Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com>
PR-URL: nodejs#18958 Fixes: nodejs#18938 Ref: nodejs/build#1145 Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com> Reviewed-By: Daijiro Wachi <daijiro.wachi@gmail.com>
https://coverage.nodejs.org/ displays nothing new since nine days. I feel something has gone wrong here?
/cc @mhdawson
The text was updated successfully, but these errors were encountered: