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

tools: do not build addons during compilation #6723

Merged
merged 1 commit into from
May 13, 2016

Conversation

MylesBorins
Copy link
Contributor

Checklist
  • tests and code linting passes
  • the commit message follows commit guidelines
Affected core subsystem(s)

Tools

Description of change

The current makefile runs both cctest and build-addons in parallel
under the assumption that both rely on all. Unfortunately
build-addons does not rely on all, and there is an edge case where
by it is possible to call build-addons while compilation is still
happening.

This patch takes the simplest route by forcing build-addons and
cctest to run in sequence like the other test targets. This ensures
that build-addons will never be run during compilation.

It would be possible to modify build-addons to rely on all but it
would be a much more aggressive change to the MAKEFILE for a fairly
minor perf bump, as cctest is so fast.

@MylesBorins MylesBorins added build Issues and PRs related to build files or the CI. tools Issues and PRs related to the tools directory. labels May 12, 2016
@MylesBorins
Copy link
Contributor Author

/cc @nodejs/build @bnoordhuis

@bnoordhuis
Copy link
Member

LGTM

The current makefile runs both `cctest` and `build-addons` in parallel
under the assumption that both rely on `all`. Unfortunately
`build-addons` does not rely on all, and there is an edge case where
by it is possible to call `build-addons` while compilation is still
happening.

This patch takes the simplest route by forcing `build-addons` and
`cctest` to run in sequence like the other test targets. This ensures
that `build-addons` will never be run during compilation.

It would be possible to modify `build-addons` to rely on `all` but it
would be a much more aggressive change to the MAKEFILE for a fairly
minor perf bump, as cctest is so fast.

PR-URL: nodejs#6723
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
@MylesBorins MylesBorins merged commit 5d64ff4 into nodejs:master May 13, 2016
evanlucas pushed a commit that referenced this pull request May 17, 2016
The current makefile runs both `cctest` and `build-addons` in parallel
under the assumption that both rely on `all`. Unfortunately
`build-addons` does not rely on all, and there is an edge case where
by it is possible to call `build-addons` while compilation is still
happening.

This patch takes the simplest route by forcing `build-addons` and
`cctest` to run in sequence like the other test targets. This ensures
that `build-addons` will never be run during compilation.

It would be possible to modify `build-addons` to rely on `all` but it
would be a much more aggressive change to the MAKEFILE for a fairly
minor perf bump, as cctest is so fast.

PR-URL: #6723
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
@MylesBorins MylesBorins deleted the fix-make-test branch June 13, 2016 18:05
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. tools Issues and PRs related to the tools directory.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants