On 18/01/15 at 18:43 +0100, Jérémy Lal wrote: > Le dimanche 18 janvier 2015 à 10:04 +0100, Lucas Nussbaum a écrit : > > On 18/01/15 at 02:45 +0100, Jérémy Lal wrote: > > > Le dimanche 18 janvier 2015 à 01:42 +0100, Lucas Nussbaum a écrit : > > > > 8<-------- > > > > > > http://aws-logs.debian.net/ftbfs-logs/2015/01/17/node-tap_0.4.13-1_jessie.log > > > > > > I'd like to know the output of > > > nodejs -e "console.log(process.platform)" > > > > > > on that build machine, to see if it is nodejs that sets a wrong > > > process.platform or if it is this node-tap test that assumes something > > > wrong about the linux platform. > > > > Hi, > > > > # nodejs -e "console.log(process.platform)" > > linux > > On linux platform the test expects exit code 128 + SIGTERM to be > returned and on other platforms just SIGTERM. > > Fixing this test is easy, but since this is the first time it fails, > is it possible the platform the tests were run on could be the cause of > the different exit code ?
Erm, I really don't know. There shouldn't be anything specific to the testbed that should have an influence here... But I can give you access to a VM if you want to dig further. Lucas _______________________________________________ Pkg-javascript-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
