-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
test: remove AIX guard in fs-options-immutable #12687
test: remove AIX guard in fs-options-immutable #12687
Conversation
if (!common.isAix) { | ||
// TODO(thefourtheye) Remove this guard once | ||
// https://github.com/nodejs/node/issues/5085 is fixed | ||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we just get rid of this start brace and its matching end brace and re-indent the enclosed code?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All the other tests also have this block thing. I thought it would be consistent. If you want to remove it, I can do it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well IMHO it's excessive since it doesn't (directly) provide scoping for any variables (or any code for that matter). I don't know how everyone else feels about it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't removing the outer block still be consistent with the rest of the test because everything inside that block scope is itself block-scoped? So you'd end up with this block-scoped code?:
{
let watch;
assert.doesNotThrow(() => {
watch = fs.watch(__filename, options, common.noop);
});
watch.close();
}
{
assert.doesNotThrow(() => fs.watchFile(__filename, options, common.noop));
fs.unwatchFile(__filename);
}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yeah, makes sense. Removed that block now...
The fs watch test was not run on AIX till now because of the known issue, nodejs#5085. Now that it is completed, this guard can be removed.
c54f8a5
to
aafd390
Compare
CI Run: https://ci.nodejs.org/job/node-test-pull-request/7700/ (after removing the block) |
LGTM |
LGTM but I'd appreciate a review from @gireeshpunathil |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good to me, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Landed in b16869c , thanks @thefourtheye ! |
The fs watch test was not run on AIX till now because of the known issue, #5085. Now that it is completed, this guard can be removed. PR-URL: #12687 Reviewed-By: Gibson Fahnestock <[email protected]> Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Brian White <[email protected]>
Depends on #7831 which is |
The fs watch test was not run on AIX till now because of the known
issue, #5085. Now that it is
completed, this guard can be removed.
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
fs aix test
@nodejs/platform-aix