Uh oh!
There was an error while loading. Please reload this page.
test: improve check in test-os - #14655
Conversation
Trott
commented
Aug 7, 2017
There was a problem hiding this comment.
Not a big deal but FWIW, the fltr const name is now inconsistent with the filter used in the win32 case
There was a problem hiding this comment.
Can you leave the name as filter and just break the line on the && operator.
There was a problem hiding this comment.
Can you leave the name as filter and just break the line on the && operator.
The check for `os.networkInterfaces()` in `test-os.js` may be too strict. It's apparently possible for a machine to be configured with multiple IPv4 loopback interfaces. Increase specificity of filter to check on only the object we expect. Fixes: nodejs#14654
| const filter = | ||
| (e) => e.address === '127.0.0.1' && e.netmask === '255.0.0.0'; | ||
| const actual = interfaces.lo.filter(filter); | ||
| const expected = [{ address: '127.0.0.1', netmask: '255.0.0.0', |
There was a problem hiding this comment.
[warning 🚨 scope-creep]
AFAICT expected and the asserting could be hoisted, and switch replaced with if or trinary for selecting interfaces.lo / interfaces['Loopback Pseudo-Interface 1']
There was a problem hiding this comment.
Some reasons to maybe not do that:
If we want to add macOS to the switch statement (in another PR), it will have a different
expectedvalue. (The MAC address is different. Yes, the MAC address is different on Mac. Ha ha, ha ha, gosh, I'm funny.)Probably don't want to replace the
switchbecause we need a do-nothingdefaultfor macos, smartos... A switch makes sense here, I think. I mean, you can make it work with anif, of course. But I think this more verbose code is actually more readable even though it does violate DRY. (I often don't value DRY much in tests, TBH.)
Even if I'm wrong about that evaluation... must...resist....scope creep.
refack
commented
Aug 8, 2017
👍
Apple SMH... |
Trott
commented
Aug 10, 2017
Landed in 2923ed1 |
The check for `os.networkInterfaces()` in `test-os.js` may be too strict. It's apparently possible for a machine to be configured with multiple IPv4 loopback interfaces. Increase specificity of filter to check on only the object we expect. PR-URL: nodejs#14655Fixes: nodejs#14654 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
The check for `os.networkInterfaces()` in `test-os.js` may be too strict. It's apparently possible for a machine to be configured with multiple IPv4 loopback interfaces. Increase specificity of filter to check on only the object we expect. PR-URL: #14655Fixes: #14654 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
The check for `os.networkInterfaces()` in `test-os.js` may be too strict. It's apparently possible for a machine to be configured with multiple IPv4 loopback interfaces. Increase specificity of filter to check on only the object we expect. PR-URL: #14655Fixes: #14654 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
The check for
os.networkInterfaces()intest-os.jsmay be toostrict. It's apparently possible for a machine to be configured with
multiple IPv4 loopback interfaces. Increase specificity of filter to
check on only the object we expect.
Fixes: #14654
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passesAffected core subsystem(s)
test os