Source: node-grunt-contrib-copy Version: 1.0.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386
Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): > at Object.<anonymous> (/usr/lib/nodejs/nodeunit/lib/core.js:236:16) > at /usr/lib/nodejs/nodeunit/lib/core.js:236:16 > at Object.exports.runTest (/usr/lib/nodejs/nodeunit/lib/core.js:70:9) > at /usr/lib/nodejs/nodeunit/lib/core.js:118:25 > at /usr/lib/nodejs/nodeunit/deps/async.js:513:13 > at iterate (/usr/lib/nodejs/nodeunit/deps/async.js:123:13) > at /usr/lib/nodejs/nodeunit/deps/async.js:134:25 > at /usr/lib/nodejs/nodeunit/deps/async.js:515:17 > at Immediate._onImmediate (/usr/lib/nodejs/nodeunit/lib/types.js:146:17) > at processImmediate [as _immediateCallback] (timers.js:396:17) > > > ✔ copy - timestamp_changed > > [1m[31mFAILURES: [39m[22m2/17 assertions failed (201ms) > debian/rules:13: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2017/04/18/node-grunt-contrib-copy_1.0.0-1_testing-i386.log 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! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures.
