-
Notifications
You must be signed in to change notification settings - Fork 166
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
CI job request: daily coverage job without Intl #2596
Comments
I assume it would just contribute the coverage to https://app.codecov.io/gh/nodejs/node, right? If so then I don't see any issue and seems like a good idea. |
As I understand the current status on this one, there's an in progress attempt to do this as a GitHub action: nodejs/node#37954 FWIW the Windows coverage job looks to have been broken for some time #2645 |
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
Still not ready to give up on this... |
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
@Trott can we close now that nodejs/node#37954 has landed? |
If there's consensus to abandon our own coverage in coverage.nodejs.org and rely on codecov.,io, then yes. If not, then we probably want to get it added to coverage.nodejs.org. I'm fine if you close this. |
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
What do we all think about the idea of trying to set up a third test coverage job (to go along with the Linux one and the Windows one) to run Node.js compiled without Intl support? That would allow us to complete coverage in files like lib/internal/util/inspect.js.html. There's already a Jenkins job that does tests without Intl (https://ci.nodejs.org/job/node-test-commit-linux-containered/nodes=ubuntu1804_sharedlibs_withoutintl_x64/). I think we'd just need to modify it to do coverage, run nightly, and push results to the right place(s).
The text was updated successfully, but these errors were encountered: