-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
Nightly coverage report outdated #1988
Comments
I see the same thing. There have been a few issues with machines on which the coverage job runs, and it may also be a change that landed as well. Hoping to look at that later today. |
We also had some unrelated issues with the main node.js site hosting but until we get the jobs generating the updates working again there is no evidence there is a problem on that side. |
One related issue: nodejs/node#25543. There is still something else going on with the main job but we need 25543 landed as at least part of getting the coverage jobs going again. |
nodejs/node#25543 is now landed and coverage job is now working again and should run nightly, but now need to see if the issues with the main site have affected the replication of the data. |
I think main site looks good. We should see updates to the coverage data going forward. @jeromecovington, please confirm you think things are ok again and then close. |
URL shows updated coverage (with a week missing). Thanks! |
At https://coverage.nodejs.org/ I am only seeing coverage up to January 10, 2019 (it's January 16 as of this writing).
The text was updated successfully, but these errors were encountered: