• Bug#1103091: node-performance-now: FTBFS in testing/i386: dh_auto_test:

    From Lucas Nussbaum@21:1/5 to All on Mon Apr 14 13:50:01 2025
    Source: node-performance-now
    Version: 2.1.0+debian-4
    Severity: serious
    Justification: FTBFS
    Tags: trixie sid ftbfs
    User: lucas@debian.org
    Usertags: ftbfs-20250414 ftbfs-trixie

    Hi,

    During a rebuild of all packages in testing (trixie), your package failed
    to build on i386.


    Relevant part (hopefully):
    make[1]: Entering directory '/build/reproducible-path/node-performance-now-2.1.0+debian'
    coffee --compile -m --output lib/ src/
    make[1]: Leaving directory '/build/reproducible-path/node-performance-now-2.1.0+debian'
    dh_auto_test --buildsystem=nodejs
    mkdir -p node_modules
    ln -s ../debian/tests/test_modules/call-delayed node_modules/call-delayed
    ln -s ../debian/tests/test_modules/chai-increasing node_modules/chai-increasing
    ln -s ../. node_modules/performance-now
    /bin/sh -ex debian/tests/pkg-js/test
    + mocha --require coffee-script/register test/performance-now.coffee test/scripts.coffee


    now
    undefined reported time differs at most 1ms from a freshly reported uptime
    undefined two subsequent calls return an increasing number
    undefined has less than 20 microseconds overhead
    undefined can be called 1 million times in under 1 second (averaging under 1 microsecond per call) (161ms)
    undefined for 10,000 numbers, number n is never bigger than number n-1 (60ms)
    undefined shows that at least 0.2 ms has passed after a timeout of 1 ms
    undefined shows that at most 3 ms has passed after a timeout of 1 ms
    undefined shows that at least 190ms ms has passed after a timeout of 200ms (203ms)
    undefined shows that at most 220 ms has passed after a timeout of 200ms (201ms)

    scripts/initital-value.coffee (module.uptime(), expressed in milliseconds)
    undefined printed 294.974
    undefined printed a value above 80
    undefined printed a value below 350

    scripts/delayed-require.coffee (sum of uptime and 250 ms delay`)
    undefined printed 482.169
    undefined printed a value above 340
    undefined printed a value below 600

    scripts/delayed-call.coffee (sum of uptime and 250 ms delay`)
    undefined printed 619.429
    undefined printed a value above 340
    1) printed a value below 600


    17 passing (665ms)
    1 failing

    1) scripts/delayed-call.coffee (sum of uptime and 250 ms delay`)
    printed a value below 600:

    AssertionError: expected 619.429 to be below 600
    + expected - actual

    -619.429
    +600

    at Context.<anonymous> (test/scripts.coffee:21:45)
    at callFn (/usr/share/nodejs/mocha/lib/runnable.js:364:21)
    at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:352:5)
    at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:677:10)
    at /usr/share/nodejs/mocha/lib/runner.js:800:12
    at next (/usr/share/nodejs/mocha/lib/runner.js:592:14)
    at /usr/share/nodejs/mocha/lib/runner.js:602:7
    at next (/usr/share/nodejs/mocha/lib/runner.js:485:14)
    at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:570:5)
    at processImmediate (node:internal/timers:483:21)




    + exit 77
    dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 77


    The full build log is available from: http://qa-logs.debian.net/2025/04/14/node-performance-now_2.1.0+debian-4_testing-i386.log

    All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250414;users=lucas@debian.org
    or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250414&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

    A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

    If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects

    If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)