Source: node-performance-now Version: 2.1.0+debian-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm
Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > coffee --compile -m --output lib/ src/ > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > 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 > (node:2928307) [DEP0005] DeprecationWarning: Buffer() is deprecated due to > security and usability issues. Please use the Buffer.alloc(), > Buffer.allocUnsafe(), or Buffer.from() methods instead. > (Use `node --trace-deprecation ...` to show where the warning was created) > > > 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) (145ms) > undefined for 10,000 numbers, number n is never bigger than number n-1 > (80ms) > 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 (201ms) > 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 138.579 > 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 588.16 > 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 451.145 > undefined printed a value above 340 > undefined printed a value below 600 > > scripts/difference.coffee > undefined printed 0.002 > 1) printed a value above 0.002 > undefined printed a value below 0.07 > > > 20 passing (663ms) > 1 failing > > 1) scripts/difference.coffee > printed a value above 0.002: > > AssertionError: expected 0.002 to be above 0.002 > + expected - actual > > > at Context.<anonymous> (test/scripts.coffee:26:47) > at callFn (/usr/share/nodejs/mocha/lib/runnable.js:366:21) > at Test.Runnable.run (/usr/share/nodejs/mocha/lib/runnable.js:354:5) > at Runner.runTest (/usr/share/nodejs/mocha/lib/runner.js:678:10) > at /usr/share/nodejs/mocha/lib/runner.js:801:12 > at next (/usr/share/nodejs/mocha/lib/runner.js:593:14) > at /usr/share/nodejs/mocha/lib/runner.js:603:7 > at next (/usr/share/nodejs/mocha/lib/runner.js:486:14) > at Immediate._onImmediate (/usr/share/nodejs/mocha/lib/runner.js:571:5) > at processImmediate (internal/timers.js:464: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/2022/04/12/node-performance-now_2.1.0+debian-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220412;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220412&fusertaguser=lu...@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 marking 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.
