You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current native addon coverage within the regular Node.js CI run is currently not adequate to cover the typical native addon cycle. This is painfully illustrated by the issue leading up to this fix: nodejs/node#20939.
There have been discussions in the past about improving the addons support in the regular CI, but until that happens, have a CI job that specifically covers the typical native addon workflow would be ideal.
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.
Activity
maclover7 commentedon May 24, 2018
@jasnell What would the CI job run? If it's a bash script, shouldn't be too hard to setup
github-actions commentedon Mar 10, 2020
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.