[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-javascript-devel


[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, checking whether something is "fast enough" or an algorithm is
O(n) vs O(n^2) and timing that is essentially relying on the machine not
being under load or is otherwise slow.

I am sure you would agree the former is problematic and not even remotely
determinstic! The latter is borderline, but when you can't rely on test
failures being genuine test failures, you psychologically start to demote
them in your mind in terms of importance and whether you should care about
the,.

> I think it is practical to give up waiting for a response some point.
> Even Debian's buildds give up after 150 minutes.

Mm, as a sanity check for the integrity of the test/build platform, timing
out after X hours or so makes sense and I have no problem with this. It's
just the stuff on the order of Y seconds that is a little bit more difficult
to justify. :)

(Can this test really not reliably detect whether something was killed/
spawned...?)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

-- 
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] 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 timeouts in tests?

I think it is practical to give up waiting for a response some point.
Even Debian's buildds give up after 150 minutes.

Regards
Graham

-- 
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] 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 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.)


-- 
891736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-marked-man
Version: 0.3.0-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-marked-man.html

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/node-marked-man-0.3.0'
nodejs test/compare.js
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/blockquotes.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/definition_list_syntax.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/dots_at_line_start_test.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/ellipses.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/entity_encoding_test.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/graves.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/links.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/markdown_syntax.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/nested_list_with_code.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/pre_block_with_quotes.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/table.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/man/underline_spacing_test.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/links.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/graves.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/entity_encoding_test.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/ellipses.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/dots_at_line_start_test.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/definition_list_syntax.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/blockquotes.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/nested_list_with_code.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/markdown_syntax.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/pre_block_with_quotes.err
Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/underline_spacing_test.err
:173: warning [p 1, 2.0i, div `3tbd17,3', 0.0i]: cannot adjust 
line
:272: warning [p 1, 2.0i, div `3tbd28,3', 0.2i]: cannot adjust 
line
:671: warning [p 1, 2.0i, div `3tbd73,0', 0.0i]: cannot adjust 
line
warning: file `', around line 18:
  table wider than line width
warning: file `', around line 13:
  table squeezed horizontally to fit line length

Test failure, result written in 
/build/1st/node-marked-man-0.3.0/test/out/table.err
Failed tests:  12
make[1]: *** [debian/rules:18: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: node-marked-man
Source-Version: 0.3.0-2

We believe that the bug you reported is fixed in the latest version of
node-marked-man, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 891...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated node-marked-man package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-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: 

[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 increasing the timeout at
all: I'm pretty hardcode on tests being determinstic so merely increasing
the wait time feels especially gross to me. :)

So, indeed, another solution is really required but alas I'm really not
familiar with this particular test nor this package in general so I would
not be able to comment with any authority.

Have you tried speaking to upstream?


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

-- 
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] 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 Lal 
Description:
 node-marked-man - Markdown to man page conversion - Node.js
Closes: 891736
Changes:
 node-marked-man (0.3.0-2) unstable; urgency=medium
 .
   * Drop node to nodejs renaming patch
   * Depends node-marked >= 0.3.9~
   * Change Section to javascript
   * Standards-Version 4.1.3
   * Move to salsa js-team
   * Fix test for marked 0.3.9 (Closes: #891736)
   * Remove Testsuite field
   * Do not override dh_auto_test
Checksums-Sha1:
 ed692310dae3f4b8bd7c6310f7611c7f14ed34be 2108 node-marked-man_0.3.0-2.dsc
 65ac9d67cf33ab4a66593c7a3d40974eef9dd291 3048 
node-marked-man_0.3.0-2.debian.tar.xz
 b1ca374cd4c9b2e2a5f48c438f3d3e2c7c384d66 6084 
node-marked-man_0.3.0-2_source.buildinfo
Checksums-Sha256:
 0829855bc3a92c0b43d984587d10fc6cdbdbff83f48a1687a656ae68d2318dcd 2108 
node-marked-man_0.3.0-2.dsc
 e58a46dcfe5a43d62353b9ff6692f5380de5d079e03eda85a038c8c15236e3c7 3048 
node-marked-man_0.3.0-2.debian.tar.xz
 328d27e8f00f44e43feddfae79550deeb25c606f226e6e96dd3bf3e8108636fd 6084 
node-marked-man_0.3.0-2_source.buildinfo
Files:
 0cbba2af49dc118cd6c6ea5da66e633b 2108 javascript optional 
node-marked-man_0.3.0-2.dsc
 56e2b758ea2ffd8455a58b7149e2102b 3048 javascript optional 
node-marked-man_0.3.0-2.debian.tar.xz
 3d2c1835b77b03b0af35df60262a382c 6084 javascript optional 
node-marked-man_0.3.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAlrI5lQSHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN0fRkQAKLW3EAw8UXzd45lrrhZQA7Gb83lIrfO
J53CE11fsaSmvB7nVjdRcYuCAFrkBJVhoZ1YFQJCtN+wcOOLjNA7IrUgGFaOGvzB
uS7J/9c8bqoENqxjQIVUeTSO2yXwzoW6M2LTlEJyUN+QXqUjhC3wK4Ne4+Goi8fF
iNVwpEhKnB7Ikh/Wm3D6L9oufhrpLHCyG5Tr4nR1TCGvztUJVn97aGvjW+eXfNqK
oG0Bm8r13bR/sCwyBV6NSzll1PhD1JTQXBhPl6ZQAKtfDU1J+VUM4iECoMi+Bf6C
jrbBqbHhsgJvyusYyM5bsUcqWDXd5ADOQAgDE5O+8T3t42xGLhfFjjLqAhKcOUc6
aQ4xr5lufjPJyg8rVVMHM+dV1thSR8hiIaSaBJg2ZtW6yHcGz7+fW8Cf43Ov7fYC
pB76WZ/agOJA/Kw8H2InfD4P7b3mwDEQRX6stoNFWKW34gaCkn7DktXXnx269Q5t
NN+gA0O/h9tj9S+XAVLwggOndGcjJjvnZ7US0lStVvR93cQ7cBZuE1SAJ9/BaKP0
Foo01oH3WNZ+vABfgA8DB7Vd3Z3M9D7RWChRNXa4RnHZK5zjddHnn741bJ2czJ5X
XhVyiBSk1kdPd0QTg2GCMZVnDxol/crBt1gT/BVaIbVDsNfg8tFePVqhGLiMfUn5
gEp1dpDQEP/l
=7/Aq
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

-- 
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] 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 and debian/tests/control to allow nodejs to migrate.

Chris, you wrote "...the test would still be unreliable whatever value
you choose", can you propose something other than increasing the
timeout?

Regards
Graham


[1] http://autopkgtest.ubuntu.com/packages/node-liftoff/bionic/armhf
[2] http://autopkgtest.ubuntu.com/packages/node-liftoff/bionic/arm64

-- 
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-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] 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