-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
[v4.x backport] Use external headers in addons tests #16550
Conversation
Just backporting one commit (3c85f4e) from #6734, and #7947. Using internal headers like @MylesBorins Given that the rc is already out, if you don't want to pick this up then I understand. This cherry-picked cleanly (except for files that don't exist on 4.x). |
a9f67ad
to
34d2d1e
Compare
@gibfahn Can you also update |
landed in cb92f93 |
@MylesBorins I think you only landed one of the two commits here, could you include @bnoordhuis 's commit as well? I'll rebase on v4.x-staging. |
There is no real need and it causes endless grief on Windows with some of the upcoming changes. PR-URL: nodejs#6734 Backport-PR-URL: nodejs#16550 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
4616dd8
to
b520c67
Compare
Rebased and removed the commit that already landed, @MylesBorins PTAL. |
aw shucks, second commit landed in b19c123 |
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
test/addons