-
-
Notifications
You must be signed in to change notification settings - Fork 31.5k
deps: illumos madvise() pre-and-post-illumos#14418 #58237
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
base: main
Are you sure you want to change the base?
Conversation
In illumos, madvise(3C) now takes `void *` for its first argument post-illumos#14418, but uses `caddr_t` pre-illumos#14418. This fix will detect if the illumos is pre-or-post-illumos#14418 so builds can work either way.
Review requested:
|
Currently testing on a post-illumos#14418 environment. The Jenkins agents for |
This change should be a literal NOP for ANY OTHER BUILD PLATFORM, even Oracle Solaris, since the |
Do I have to promote this to a non-draft PR to get Jenkins to run a build? |
Failed to start CI⚠ No approving reviews found ✘ Refusing to run CI on potentially unsafe PRhttps://github.com/nodejs/node/actions/runs/14914717962 |
Thank you @cjihrig ! |
This is good news and I've updated this PR to ready-for-review. The Node CI for SmartOS uses a pre-illumos#14418 illumos revision, and my local build uses a post-illumos#14418 revision. The same code now works before-and-after the illumos change in question. As mentioned earlier, this may allow less byzantine build agents for the Node CI. The Node CI results are above, and my local build's test results were all successfull but one failure:
Which was the same one when I updated the V8 pointer-updates for illumos. |
In illumos, madvise(3C) now takes
void *
for its first argument post-illumos#14418, but usescaddr_t
pre-illumos#14418. This fix will detect if the illumos is pre-or-post-illumos#14418 so builds can work either way.Cf. https://illumos.org/issues/14418