Hi Graham and thanks for bringing this up again. Il 07/04/2018 18:13, Graham Inggs ha scritto: > Hi > > This situation seems to get worse with each new version of nodejs. > > In Ubuntu, where autopkgtests are run for every release architecture, > node-liftoff failed on armhf [1] and arm64 [2] since the upload of > nodejs 8.9.3. > > We resorted to increasing the timeout from 5000 to 10000 in > debian/rules and debian/tests/control to allow nodejs to migrate. > > Chris, you wrote "...the test would still be unreliable whatever value > you choose", can you propose something other than increasing the > timeout? > > Regards > Graham > > [1] http://autopkgtest.ubuntu.com/packages/node-liftoff/bionic/armhf > [2] http://autopkgtest.ubuntu.com/packages/node-liftoff/bionic/arm64
Upstream's CI does not test above node.js 6. I have raised that here: https://github.com/js-cli/js-liftoff/issues/96 Nonetheless it may be worth updating liftoff to 2.5.0; I am going to try that. Two new packages are required, see: https://lists.alioth.debian.org/pipermail/pkg-javascript-devel/2018-April/025746.html Any help with sponsoring them is welcome. I also need to update: - node-findup-sync 0.4.3-1 -> 2.0.0 - node-micromatch 2.3.11-1 -> 3.0.4 - node-detect-file 0.1.0-1 -> 1.0.0 - node-resolve-dir 1.0.0-1 -> 1.0.1 - node-flagged-respawn -> 0.3.2-1 -> 1.0.0 The latter in particular sounds promising for the "Liftoff launch should respawn if process.argv has values from v8flags in it" test failures. flagged-respawn also has a test suite itself which can be enabled since we now have node-v8flags in Debian. Maybe we catch it there ! Expect more RFSs over the next few days ... Paolo -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
