Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

Build failure on Ubuntu 12.04 #2

Closed
targos opened this issue May 9, 2017 · 9 comments
Closed

Build failure on Ubuntu 12.04 #2

targos opened this issue May 9, 2017 · 9 comments

Comments

@targos
Copy link
Member

targos commented May 9, 2017

https://ci.nodejs.org/job/node-test-commit-linux/9732/nodes=ubuntu1204-64/console

g++ -pthread -rdynamic -m64 -m64  -o /home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/mksnapshot -Wl,--start-group /home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/obj.target/mksnapshot/deps/v8/src/snapshot/mksnapshot.o /home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/obj.target/deps/v8/src/libv8_base.a /home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/obj.target/deps/v8/src/libv8_libbase.a /home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/obj.target/deps/v8/src/libv8_nosnapshot.a /home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/obj.target/deps/v8/src/libv8_libplatform.a /home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/obj.target/tools/icu/libicui18n.a /home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/obj.target/deps/v8/src/libv8_libsampler.a /home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/obj.target/tools/icu/libicuucx.a /home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/obj.target/tools/icu/libicudata.a /home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/obj.target/tools/icu/libicustubdata.a -ldl -lrt -Wl,--end-group
  LD_LIBRARY_PATH=/home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/lib.host:/home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/lib.target:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; cd ../deps/v8/src; mkdir -p /home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/obj.target/v8_snapshot/geni; "/home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/mksnapshot" --startup_src "/home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/obj.target/v8_snapshot/geni/snapshot.cc" ""
/home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/mksnapshot: error while loading shared libraries: cannot allocate memory in static TLS block
make[2]: *** [/home/iojs/build/workspace/node-test-commit-linux/nodes/ubuntu1204-64/out/Release/obj.target/v8_snapshot/geni/snapshot.cc] Error 127
@targos
Copy link
Member Author

targos commented May 16, 2017

Still happening: https://ci.nodejs.org/job/node-test-commit-linux/9879/nodes=ubuntu1204-64/console

@targos
Copy link
Member Author

targos commented May 22, 2017

Also happens with V8 5.9: https://ci.nodejs.org/job/node-test-commit-linux/10054/nodes=ubuntu1204-64/console

@nodejs/lts @nodejs/ctc I think we have to choose now (i.e. before the 8.0.0 release) if we still want to support this system or if we are going to fix this.

@targos targos mentioned this issue May 22, 2017
Closed
@bnoordhuis
Copy link
Member

It's EOL, drop it!

@gibfahn
Copy link
Member

gibfahn commented May 22, 2017

I think we have to choose now (i.e. before the 8.0.0 release) if we still want to support this system or if we are going to fix this.

All the discussion has been about dropping support within a release, I don't think anyone is opposed to dropping support before v8.x.

💯 to dropping it.

@cjihrig
Copy link

cjihrig commented May 22, 2017

+1 to dropping it.

@mhdawson
Copy link
Member

I'm +1 for dropping it in 8.x and later

@gibfahn
Copy link
Member

gibfahn commented May 24, 2017

I can add an equivalent of nodejs/build#688 (comment) to skip it in the test job if there are no objections.

@gibfahn
Copy link
Member

gibfahn commented May 24, 2017 •
edited
Loading

Changed the clang check to an ubuntu1204 check in node-test-commit-linux, the only label with clang in the name was ubuntu1204-clang341-64 (which would still be picked up by this), and that has been disabled anyway.

if [[ "$nodes" =~ ubuntu1204 && ${MAJOR_VERSION} -gt 7 ]]; then
  RUN_TESTS="DONT_RUN"
  SKIP_MESSAGE="ubuntu1204 is not supported for version 8 and above, skipping"

Confirmed that the skipping works.

@targos
Copy link
Member Author

targos commented May 31, 2017

Thank you @gibfahn!

@targos targos closed this as completed May 31, 2017
@gibfahn gibfahn mentioned this issue Jun 2, 2017
Closed
nodejs-ci pushed a commit that referenced this issue Oct 27, 2017
@danbev
test: allow tests to pass without internet
d653f03 
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.FailsToBindToNodejsHost
make[1]: *** [cctest] Segmentation fault: 11
make: *** [test] Error 2

lldb output:

[ RUN      ] InspectorSocketServerTest.FailsToBindToNodejsHost
Process 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 + 87
libsystem_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: 0x00000001017d8888
cctest`uv__getaddrinfo_work(w=0x00007fff5fbfe210) + 72 at
getaddrinfo.c:102
    frame #5: 0x00000001017d880e
cctest`uv_getaddrinfo(loop=0x000000010287cb80, req=0x00007fff5fbfe1c8,
cb=0x0000000000000000, hostname="nodejs.org", service="0",
hints=0x00007fff5fbfe268) + 734 at getaddrinfo.c:192
    frame #6: 0x000000010171f781
cctest`node::inspector::InspectorSocketServer::Start(this=0x00007fff5fbfe658)
+ 801 at inspector_socket_server.cc:398
    frame #7: 0x00000001016ed590
cctest`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.

PR-URL: nodejs/node#16255
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: James M Snell <jasnell@gmail.com>
nodejs-ci pushed a commit that referenced this issue Dec 16, 2017
@bnoordhuis @BridgeAR
http: remove adapter frame from onParserExecute
31addac 
Remove a pointless adapter frame  by fixing up the function's formal
parameter count.  Before:

    frame #0: 0x000033257ea446d5 onParserExecute(...)
    frame #1: 0x000033257ea3b93f <adaptor>
    frame #2: 0x000033257ea41959 <internal>
    frame #3: 0x000033257e9840ff <entry>

After:

    frame #0: 0x00000956287446d5 onParserExecute(...)
    frame #1: 0x0000095628741959 <internal>
    frame #2: 0x00000956286840ff <entry>

PR-URL: nodejs/node#17693
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com>
Reviewed-By: Khaidi Chu <i@2333.moe>
@guybedford guybedford mentioned this issue Jun 17, 2019
Closed
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@bnoordhuis @targos @cjihrig @mhdawson @gibfahn