test: allow tests to pass without internet

[danbev]

Currently when running the test without an internet connection there are
two JavaScript test failures and one cctest. The cctest only fails on
Mac as far as I know. (I've only tested using Mac and Linux thus far).

This commit moves the two JavaScript tests to test/internet.

The details for test_inspector_socket_server.cc:

[ RUN ] InspectorSocketServerTest.FailsToBindToNodejsHostmake[1]: *** [cctest] Segmentation fault: 11make: *** [test] Error 2

lldb output:

[ RUN ] InspectorSocketServerTest.FailsToBindToNodejsHostProcess 63058 stopped* thread #1: tid = 0x7b175, 0x00007fff96d04384* libsystem_info.dylib`_gai_simple + 87, queue =* 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1,* address=0x0) frame #0: 0x00007fff96d04384 libsystem_info.dylib`_gai_simple + 87libsystem_info.dylib`_gai_simple:-> 0x7fff96d04384 <+87>: movw (%rdx), %ax 0x7fff96d04387 <+90>: movw %ax, -0x2a(%rbp) 0x7fff96d0438b <+94>: movq %r13, -0x38(%rbp) 0x7fff96d0438f <+98>: movq 0x18(%rbp), %rcx(lldb) bt* thread #1: tid = 0x7b175, 0x00007fff96d04384* libsystem_info.dylib`_gai_simple + 87, queue =* 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1,* address=0x0) * frame #0: 0x00007fff96d04384 libsystem_info.dylib`_gai_simple + 87 frame #1: 0x00007fff96cfe98b libsystem_info.dylib`search_addrinfo +179 frame #2: 0x00007fff96cfafef libsystem_info.dylib`si_addrinfo + 2255 frame #3: 0x00007fff96cfa67b libsystem_info.dylib`getaddrinfo + 179 frame #4: 0x00000001017d8888cctest`uv__getaddrinfo_work(w=0x00007fff5fbfe210) + 72 atgetaddrinfo.c:102 frame #5: 0x00000001017d880ecctest`uv_getaddrinfo(loop=0x000000010287cb80, req=0x00007fff5fbfe1c8,cb=0x0000000000000000, hostname="nodejs.org", service="0",hints=0x00007fff5fbfe268) + 734 at getaddrinfo.c:192 frame #6: 0x000000010171f781cctest`node::inspector::InspectorSocketServer::Start(this=0x00007fff5fbfe658)+ 801 at inspector_socket_server.cc:398 frame #7: 0x00000001016ed590cctest`InspectorSocketServerTest_FailsToBindToNodejsHost_Test::TestBody(this=0x0000000105001fd0)+ 288 at test_inspector_socket_server.cc:593

I'm not sure about the exact cause for this but when using a standalone
c program to simulate this it seems like when the ai_flags
AI_NUMERICSERV is set, which is done in inspector_socket_server.cc
line 394, the servname (the port in the FailsToBindToNodejsHost test) is
expected to be a numeric port string to avoid looking it up in
/etc/services. When the port is 0 as is it was before this commit the
segment fault occurs but not if it is non-zero.

Here is the example program I used to reproduce:

intmain(intargc, char*argv[]){structaddrinfohints, *info, *p; intres; memset(&hints, 0, sizeof(hints)); hints.ai_flags=AI_NUMERICSERV; hints.ai_socktype=SOCK_STREAM; // using "0" will segfault if there is no internet connectionif ((res=getaddrinfo("nodejs.org", "0", &hints, &info)) !=0){fprintf(stderr, "Error: %s, (%d)\n", gai_strerror(res), res); exit(1)} fprintf(stdout, "flags %d\n", info->ai_flags); fprintf(stdout, "family %d\n", info->ai_family); fprintf(stdout, "socktype %d\n", info->ai_socktype); fprintf(stdout, "protocol %d\n", info->ai_protocol)}

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• commit message follows commit guidelines

Affected core subsystem(s)

test

[danbev]

CI: https://ci.nodejs.org/job/node-test-pull-request/10780/

[mscdex]

Are the multicast tests a problem just on macOS or also Linux and/or other platforms?

[danbev]

Are the multicast tests a problem just on macOS or also Linux and/or other platforms?

They are a problem at least on MacOS and Linux. I'll give Windows a try as well and see.

[Trott]

Would it make sense to split the test files up and only put the test cases that use the internet into internet? I'm imagining that the dgram membership test does not need internet for its assert.throws() stuff but may need a network connection for the assert.doesNotThrow() parts. If I'm mistaken and talking nonsense, please disregard me.

[richardlau]

Note: internet tests are not run on the CI so there may be a slight drop in coverage.

(This is not an objection from me for this PR).

[danbev]

Would it make sense to split the test files up and only put the test cases that use the internet into internet?

I'll take a look and see what can be done.

[danbev]

@Trott I took a look and I've moved 3 tests out of test-dgram-membership.js into test/internet but did nothing for test-dgram-multicast-set-interface-lo.js as it seems did not seem worth it. Let know what you think when you get a chance.

[Trott]

@Trott I took a look and I've moved 3 tests out of test-dgram-membership.js into test/internet but did nothing for test-dgram-multicast-set-interface-lo.js as it seems did not seem worth it. Let know what you think when you get a chance.

SGTM

[danbev]

CI: https://ci.nodejs.org/job/node-test-pull-request/10987/

[danbev]

test/arm-fanned failure looks unrelated

console output:

gyp ERR! not ok Makefile:288: recipe for target 'test/addons/.buildstamp' failedmake: *** [test/addons/.buildstamp] Error 1FATAL: Unable to delete script file /tmp/jenkins1254593200766722388.shjava.nio.channels.ClosedChannelException at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142) at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:721) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Caused: hudson.remoting.RequestAbortedException at hudson.remoting.Request.abort(Request.java:331) at hudson.remoting.Channel.terminate(Channel.java:989) at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.onReadClosed(ChannelApplicationLayer.java:208) at org.jenkinsci.remoting.protocol.ApplicationLayer.onRecvClosed(ApplicationLayer.java:222) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.FilterLayer.onRecvClosed(FilterLayer.java:287) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.onRecvClosed(SSLEngineFilterLayer.java:172) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832) at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142) at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:721) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) at ......remote call to JNLP4-connect connection from static-n49-176-213-208.sbr2.nsw.optusnet.com.au/49.176.213.208:51935(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1654) at hudson.remoting.Request.call(Request.java:194) at hudson.remoting.Channel.call(Channel.java:904) at hudson.FilePath.act(FilePath.java:987) at hudson.FilePath.act(FilePath.java:976) at hudson.FilePath.delete(FilePath.java:1427) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:123) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:736) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:496) at hudson.model.Run.execute(Run.java:1737) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:421)Build step 'Execute shell' marked build as failureFATAL: nulljava.lang.NullPointerException at org.jenkinsci.plugins.credentialsbinding.impl.UnbindableDir.tempDir(UnbindableDir.java:67) at org.jenkinsci.plugins.credentialsbinding.impl.UnbindableDir.secretsDir(UnbindableDir.java:62) at org.jenkinsci.plugins.credentialsbinding.impl.UnbindableDir.access$000(UnbindableDir.java:23) at org.jenkinsci.plugins.credentialsbinding.impl.UnbindableDir$UnbinderImpl.unbind(UnbindableDir.java:84) at org.jenkinsci.plugins.credentialsbinding.impl.SecretBuildWrapper$1.tearDown(SecretBuildWrapper.java:113) at hudson.model.Build$BuildExecution.doRun(Build.java:174) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:496) at hudson.model.Run.execute(Run.java:1737) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:421)ERROR: Step ‘Publish TAP Results’ failed: no workspace for node-test-binary-arm/RUN_SUBSET=addons,label=pi1-raspbian-wheezy #11236Checking ^not okERROR: Build step failed with exceptionjava.lang.NullPointerException at hudson.plugins.textfinder.TextFinderPublisher.findText(TextFinderPublisher.java:101) at hudson.plugins.textfinder.TextFinderPublisher.perform(TextFinderPublisher.java:74) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:736) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:682) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:627) at hudson.model.Run.execute(Run.java:1762) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:421)Build step 'Jenkins Text Finder' marked build as failureNotifying upstream projects of job completionFinished: FAILURE

[danbev]

Landed in d653f03

[MylesBorins]

Should this be backported to v6.x-staging? If yes please follow the guide and raise a backport PR, if not let me know or add the dont-land-on label.