-
Notifications
You must be signed in to change notification settings - Fork 98
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
discussion: Re-establish automation to detect breaking changes #412
Comments
No9
changed the title
Re-establish automation to detect breaking changes
discussion: Re-establish automation to detect breaking changes
Sep 17, 2022
This was referenced Sep 17, 2022
@kvakil Would like to get you're thoughts on this. |
I think if we get testing of nightly + v8-canary working we'll get
largely the same benefit as having the test upstream. We can have it run
on a daily schedule and get notifications for when it fails.
This increases the chances that we roll out a version of Node.js which
does not support llnode (e.g. if nobody fixes the failure in time). This
is fine -- I don't think llnode failures should block Node.js releases.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per #287 (comment) the core project used to detect breaking changes but this has been removed. This issue is to track conversation on how the llnode project can either re-establish the tests here or provide other mitigation.
The text was updated successfully, but these errors were encountered: