samshull/node-proxy — Issue #23: build hangs on arch linux / npm 1.1.0-beta-10
Author: lloyd
Created: 2012-01-19 05:41:08+00:00
State: open

I'm seeing reproducible hangs on an arch linux VM I have provisioned in on mosso.

$ node-waf --version
waf 1.5.16 (7610:7647M)
$ node --version
v0.6.7
$ npm --version
1.1.0-beta-10

The symptom I see is hanging after this output:

$ make
BUILDING: C++ Component
Checking for program g++ or c++ : /usr/bin/g++
Checking for program cpp : /usr/bin/cpp
Checking for program ar : /usr/bin/ar
Checking for program ranlib : /usr/bin/ranlib
Checking for g++ : ok
Checking for node path : not found
Checking for node prefix : ok /usr
'configure' finished successfully (0.075s)
Waf: Entering directory `/home/lth/.npm/node-proxy/0.5.2/package/src/build'
[1/2] cxx: node-proxy.cc -> build/Release/node-proxy_1.o

Looking at the process tree, I see one python instance running with four children. strace on all of the children shows me:

futex(..., FUXTEX_WAIT_PRIVATE ....

If I force node-waf away from parallel jobs (by supplying in the makefile `-j1`) the hanging is resolved for me.

Disclaimer: I've never built software using node-waf, and I don't know how node-waf handles concurrent jobs and I don't understand node-waf's file locking. Also, a different arch linux machine (my desktop) also completely updated and on the same software versions above doesn't display this problem. Both have 4 compute cores.

I'll send a pull request, fwiw.