[Pkg-javascript-devel] Bug#858593: Reopen Bug#858593 node-mocha	doesn't build on build daemons
    Paul Gevers 
    elbrus at debian.org
       
    Fri Mar 24 20:19:15 UTC 2017
    
    
  
Control: tags help
On 03/24/17 10:19, Paul Gevers wrote:
> Yes, but on the build daemon the problems aren't over¹.
> 
> [0m  1) http should provide an example:
> [0m[31m     Uncaught Error: socket hang up[0m[90m
>     at createHangUpError (_http_client.js:213:15)
>     at Socket.socketOnEnd (_http_client.js:305:23)
>     at emitNone (events.js:72:20)
>     at Socket.emit (events.js:166:7)
>     at endReadableNT (_stream_readable.js:923:12)
>     at nextTickCallbackWith2Args (node.js:511:9)
>     at process._tickCallback (node.js:425:17)
> 
> ¹
> https://buildd.debian.org/status/fetch.php?pkg=node-mocha&arch=all&ver=1.20.1-4&stamp=1490346930&raw=0
Does anybody here have a clue how to fix such an issue? It is NOT
reproducible in my pbuilder environment, not even when I enable
networking (as sbuild is suggested to have (suggested on IRC)). It is
also not reproducible in the builds by the reproducible-builds project.
And it is also not reproducible on the debomatic.d.n service.
But it is the second time in succession (meaning 100% failure rate for
this package) that this "socket hang up" error occurred on a build daemon.
Paul
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-javascript-devel/attachments/20170324/456aa610/attachment.sig>
    
    
More information about the Pkg-javascript-devel
mailing list