Your message dated Thu, 19 Nov 2020 11:58:37 +0100
with message-id <77783799-73c7-0bc7-a7c0-bb95610d9...@debian.org>
and subject line Fixed in 4.0.0-1
has caused the Debian Bug report #975226,
regarding node-multipipe: FTBFS: test failed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
975226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975226
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-multipipe
Version: 1.0.2-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
>
>
> pipe()
> ✓ should return a stream
> ✓ should accept options
>
> pipe(a)
> ✓ should pass through to a
> ✓ should accept options
>
> pipe(a, b, c)
> ✓ should pipe internally
> ✓ should be writable
> ✓ should be readable
> ✓ should be readable and writable
> ✓ should accept options
> errors
> ✓ should reemit
> ✓ should not reemit endlessly
>
> pipe(a, b, c, fn)
> ✓ should call on finish
> ✓ should call with error once
> 1) should call on destroy
> 2) should call on destroy with error
> ✓ should accept options
> ✓ should ignore parameters on non error events
>
>
> 15 passing (37ms)
> 2 failing
>
> 1) pipe(a, b, c, fn)
> should call on destroy:
>
> Uncaught AssertionError [ERR_ASSERTION]: The expression evaluated to a
> falsy value:
>
> assert(!err)
>
> + expected - actual
>
> -false
> +true
>
> at /<<PKGBUILDDIR>>/test/multipipe.js:139:7
> at Transform.end (index.js:87:7)
> at onwriteError
> (/usr/share/nodejs/readable-stream/lib/_stream_writable.js:420:12)
> at onwrite
> (/usr/share/nodejs/readable-stream/lib/_stream_writable.js:446:11)
> at WritableState.onwrite
> (/usr/share/nodejs/readable-stream/lib/_stream_writable.js:158:5)
> at doWrite
> (/usr/share/nodejs/readable-stream/lib/_stream_writable.js:405:30)
> at writeOrBuffer
> (/usr/share/nodejs/readable-stream/lib/_stream_writable.js:394:5)
> at Transform.Writable.write
> (/usr/share/nodejs/readable-stream/lib/_stream_writable.js:303:11)
> at Transform.ondata (_stream_readable.js:719:22)
> at addChunk (_stream_readable.js:298:12)
> at readableAddChunk (_stream_readable.js:273:9)
> at Transform.Readable.push (_stream_readable.js:214:10)
> at Transform.push (_stream_transform.js:152:32)
> at Transform.afterTransform (_stream_transform.js:96:10)
> at Transform.transform._transform (test/multipipe.js:188:5)
> at Transform._read (_stream_transform.js:191:10)
> at Transform._write (_stream_transform.js:179:12)
> at doWrite (_stream_writable.js:403:12)
> at writeOrBuffer (_stream_writable.js:387:5)
> at Transform.Writable.write (_stream_writable.js:318:11)
> at Readable.ondata (_stream_readable.js:719:22)
> at Readable.read (_stream_readable.js:508:10)
> at flow (_stream_readable.js:1008:34)
> at resume_ (_stream_readable.js:989:3)
> at processTicksAndRejections (internal/process/task_queues.js:84:21)
>
> 2) pipe(a, b, c, fn)
> should call on destroy with error:
>
> Uncaught AssertionError [ERR_ASSERTION]: [NodeError: Cannot call write
> after a stream was destroyed] == [Error]
> + expected - actual
>
>
> at /<<PKGBUILDDIR>>/test/multipipe.js:153:14
> at Transform.end (index.js:87:7)
> at onwriteError
> (/usr/share/nodejs/readable-stream/lib/_stream_writable.js:420:12)
> at onwrite
> (/usr/share/nodejs/readable-stream/lib/_stream_writable.js:446:11)
> at WritableState.onwrite
> (/usr/share/nodejs/readable-stream/lib/_stream_writable.js:158:5)
> at doWrite
> (/usr/share/nodejs/readable-stream/lib/_stream_writable.js:405:30)
> at writeOrBuffer
> (/usr/share/nodejs/readable-stream/lib/_stream_writable.js:394:5)
> at Transform.Writable.write
> (/usr/share/nodejs/readable-stream/lib/_stream_writable.js:303:11)
> at Transform.ondata (_stream_readable.js:719:22)
> at addChunk (_stream_readable.js:298:12)
> at readableAddChunk (_stream_readable.js:273:9)
> at Transform.Readable.push (_stream_readable.js:214:10)
> at Transform.push (_stream_transform.js:152:32)
> at Transform.afterTransform (_stream_transform.js:96:10)
> at Transform.transform._transform (test/multipipe.js:188:5)
> at Transform._read (_stream_transform.js:191:10)
> at Transform._write (_stream_transform.js:179:12)
> at doWrite (_stream_writable.js:403:12)
> at writeOrBuffer (_stream_writable.js:387:5)
> at Transform.Writable.write (_stream_writable.js:318:11)
> at Readable.ondata (_stream_readable.js:719:22)
> at Readable.read (_stream_readable.js:508:10)
> at flow (_stream_readable.js:1008:34)
> at resume_ (_stream_readable.js:989:3)
> at processTicksAndRejections (internal/process/task_queues.js:84:21)
>
>
>
> make[1]: *** [Makefile:6: test] Error 2
The full build log is available from:
http://qa-logs.debian.net/2020/11/19/node-multipipe_1.0.2-1_unstable.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.
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 20917
--- End Message ---
