Skip to content
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

build: account for pure C sources in build-addons-napi #21797

Closed
wants to merge 1 commit into from

Conversation

addaleax
Copy link
Member

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • commit message follows commit guidelines

@addaleax addaleax added build Issues and PRs related to build files or the CI. node-api Issues and PRs related to the Node-API. fast-track PRs that do not need to wait for 48 hours to land. labels Jul 13, 2018
@nodejs-github-bot nodejs-github-bot added the build Issues and PRs related to build files or the CI. label Jul 13, 2018
@addaleax
Copy link
Member Author

CI: https://ci.nodejs.org/job/node-test-pull-request/15861/

Feel free to 👍 this comment to approve fast-tracking.

@refack
Copy link
Contributor

refack commented Jul 13, 2018

/CC @nodejs/build-files

Why is there a need for fast track?

@refack
Copy link
Contributor

refack commented Jul 13, 2018

@addaleax
Copy link
Member Author

@refack Why does there have to be a need? It makes sense to me… It’s a simple change – a one-liner in the most literal way – so it’s not like one could reasonably expect a lot of review on it.

It also fixes a real issue (that some N-API tests don’t get recompiled if they are changed, which is a bad thing), but that’s not really my point here…

@addaleax addaleax removed the fast-track PRs that do not need to wait for 48 hours to land. label Jul 13, 2018
@refack
Copy link
Contributor

refack commented Jul 13, 2018

Why does there have to be a need? It makes sense to me… It’s a simple change – a one-liner in the most literal way – so it’s not like one could reasonably expect a lot of review on it.

The 48h-72h time is not only for review, it's also a chance for Collaborators to become aware of changes. There's is a general notion of areas of expertise and code ownership, so IMHO the stakeholder should have a chance to be aware of changes.

I agree it's a simple change, but it's not trivial (changes the build/test recipe), nor does it fix a regression (AFAICT). I'd rather take it slow, especially since the last change in those lines was regressive. 57bd27e

@addaleax
Copy link
Member Author

Landed in 31ecf63

@addaleax addaleax closed this Jul 16, 2018
@addaleax addaleax deleted the n-api-makefile-c-sources branch July 16, 2018 18:09
addaleax added a commit to addaleax/node that referenced this pull request Jul 16, 2018
PR-URL: nodejs#21797
Reviewed-By: Gus Caplan <[email protected]>
Reviewed-By: Jon Moss <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Refael Ackermann <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
targos pushed a commit that referenced this pull request Jul 16, 2018
PR-URL: #21797
Reviewed-By: Gus Caplan <[email protected]>
Reviewed-By: Jon Moss <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Refael Ackermann <[email protected]>
Reviewed-By: Richard Lau <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
@targos targos mentioned this pull request Jul 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build Issues and PRs related to build files or the CI. node-api Issues and PRs related to the Node-API.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants