[Pkg-javascript-devel] Bug#891736: node-marked-man FTBFS: test failure

2018-04-07 Thread Graham Inggs
This was caused by the upload of node-marked 0.3.9+dfsg-1 -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel

[Pkg-javascript-devel] Processing of node-marked-man_0.3.0-2_source.changes

2018-04-07 Thread Debian FTP Masters
node-marked-man_0.3.0-2_source.changes uploaded successfully to localhost along with the files: node-marked-man_0.3.0-2.dsc node-marked-man_0.3.0-2.debian.tar.xz node-marked-man_0.3.0-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-

[Pkg-javascript-devel] Bug#853035: node-liftoff: Non-determistically FTBFS due to unreliable timing in tests

2018-04-07 Thread Graham Inggs
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 1 in debian/rules an

[Pkg-javascript-devel] node-marked-man_0.3.0-2_source.changes ACCEPTED into unstable

2018-04-07 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 07 Apr 2018 17:39:04 +0200 Source: node-marked-man Binary: node-marked-man Architecture: source Version: 0.3.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy

[Pkg-javascript-devel] Bug#853035: node-liftoff: Non-determistically FTBFS due to unreliable timing in tests

2018-04-07 Thread Chris Lamb
[Resending including 853...@bugs.debian.org in CC this time..] Hi Graham, Thanks for the followup. > Chris, you wrote "...the test would still be unreliable whatever value > you choose", can you propose something other than increasing the > timeout? Well, just to be 100% clear, I don't propose

[Pkg-javascript-devel] Bug#891736: marked as done (node-marked-man FTBFS: test failure)

2018-04-07 Thread Debian Bug Tracking System
Your message dated Sat, 07 Apr 2018 16:21:11 + with message-id and subject line Bug#891736: fixed in node-marked-man 0.3.0-2 has caused the Debian Bug report #891736, regarding node-marked-man FTBFS: test failure to be marked as done. This means that you claim that the problem has been dealt

[Pkg-javascript-devel] Bug#853035: node-liftoff: Non-determistically FTBFS due to unreliable timing in tests

2018-04-07 Thread Graham Inggs
Hi Chris On 7 April 2018 at 18:22, Chris Lamb wrote: > Well, just to be 100% clear, I don't propose increasing the timeout at > all: I'm pretty hardcode on tests being determinstic so merely increasing > the wait time feels especially gross to me. :) Would you please explain your objection to ti

[Pkg-javascript-devel] Bug#853035: node-liftoff: Non-determistically FTBFS due to unreliable timing in tests

2018-04-07 Thread Chris Lamb
Hi Graham, > > I'm pretty hardcore on tests being determinstic, so merely increasing > > the wait time feels especially gross to me. :) > > Would you please explain your objection to timeouts in tests? Well, we should probably separate the cases of using /timing/ in tests as part of, say, checki

[Pkg-javascript-devel] node-ip is marked for autoremoval from testing

2018-04-07 Thread Debian testing autoremoval watch
node-ip 1.1.5-1 is marked for autoremoval from testing on 2018-04-09 It is affected by these RC bugs: 892658: node-ip: node-ip FTBFS with mocha 4.0.1-3 -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-j