Source: node-tap
Version: 8.0.0-1
Severity: normal
Hi maintainer
Node-tap has been consistently failing its autopkgtests since 2016-11-13 [1].
This corresponds to the upload of node-tap 8.0.0-1.
Regards
Graham
[1] https://ci.debian.net/packages/n/node-tap/unstable/amd64/
--
Pkg-javascript-d
Source: nodejs
Version: 4.6.1~dfsg-1
Severity: wishlist
Tags: patch
Hi Maintainer
Nodejs has been failing its autopkgtests since 2016-11-02 [1].
This corresponds with the upload of openssl 1.0.2j-1 [2].
The attached patch from Ubuntu seems to fix this.
Additionally, since the upload of nodejs 4
Source: node-isexe
Version: 1.1.2-1
Severity: wishlist
Tags: patch
Hi Maintainer
Node-isexe has been failing its autopkgtests since 2016-11-14 [1].
This corresponds with the upload of node-tap 8.0.0-1.
Excerpt from a recent failing test log [2]:
adt-run [22:05:18]: test command1: -
Control: reopen -1
Autopkgtests for nodejs 4.7.2~dfsg-2 still fail[1] with:
not ok 663 parallel/test-process-config
---
duration_ms: 0.89
severity: fail
stack: |-
fs.js:549
return binding.open(pathModule._makeLong(path),
stringToFlags(flags), mode);
^
E
Source: node-policyfile
Version: 0.0.5-3
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful autopkgtest
Hi Maintainer
Since the upload of nodejs 6, node-policyfile's autopkgtests have been
failing [1] with the following error:
autopkgtest [09:36:46]: summa
Source: node-node-redis
Version: 0.1.7-1
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful autopkgtest
Hi Maintainer
Since the upload of nodejs 6, node-node-redis's autopkgtests have been
failing [1] with the following error:
autopkgtest [08:56:34]: summ
Source: node-browserify-sign
Version: 4.0.4-1
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful autopkgtest
Hi Maintainer
Since the upload of nodejs 6, node-browserify-sign's autopkgtests have
been failing [1] with the following error:
autopkgtest [00:53:25]: @@@
Source: node-tap
Version: 8.0.0-4
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful autopkgtest
Hi Maintainer
Since the upload of nodejs 6, node-tap's autopkgtests have been failing
[1] with the following error:
# failed 3 of 47 tests
# skip: 7
# time=113059.894ms
autopkgtest
Source: node-foreground-child
Version: 1.5.6-1
Severity: serious
Hi Maintainer
Node-foreground-child FTBFS in unstable:
https://tests.reproducible-builds.org/debian/history/node-foreground-child.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-foreground-child.html
Source: node-babylon
Version: 6.14.1-1
Severity: serious
Hi Maintainer
Node-babylon has a build dependency on nodejs-legacy which is no longer
in the archive. With this dependency removed, the build fails on a
machine without external network access:
...
HOME=/tmp npm install babel-cli roll
Source: node-babel
Version: 6.25.0+dfsg-1
Severity: serious
Hi Maintainer
Node-babel fails to build on a machine without external network access:
...
npm install
npm ERR! Linux 4.4.0-92-generic
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v6.11.2
npm ERR! npm v3.5.2
npm
Control: reopen -1
Hi
Autopkgtests are still failing. Would you please keep the bug open
until they are fixed?
It currently shows up as resolved in our tagged bugs report [1].
Regards
Graham
[1]
https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive=both;tag=autopkgtest;users=ubuntu-de...@list
Control: severity -1 serious
Since the upload of nodejs 8.9.3, this warning has turned into a failure.
As far a I can tell, this package has no reverse-dependencies, should
it be considered for removal?
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://list
Source: node-ultron
Version: 1.1.1-1
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic autopkgtest
Hi Maintainer
Since the upload of nodejs 8.9.3~dfsg-5 to unstable on 2018-01-04,
node-ultron's 'mytest1' autopkgtest has been failing [1].
autopkgtest [00:08:30]: test command1: no
Source: node-foreground-child
Version: 1.5.6-4
Severity: serious
Some recent change in unstable makes node-foreground-child FTBFS:
https://tests.reproducible-builds.org/debian/history/node-foreground-child.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-foreground-ch
Control: tags -1 + patch
The attached patch fixes the failing test, as per upstream's commit:
https://github.com/unshiftio/ultron/commit/dd787a2c3d3caaa3327918d1ecdabe56ecc3e0b1
--- a/debian/tests/mytest1.js
+++ b/debian/tests/mytest1.js
@@ -195,7 +195,7 @@
// In Node.js 8+ `EventEmitter#
Source: node-source-map
Version: 0.6.0+dfsg-1
Severity: serious
Hi Maintainer
Upgrading node-source-map to version 0.6.0 broke node-grunt-contrib-concat.
As it can be seen in the debci logs [1], the failures started on 2017-09-28.
Regards
Graham
[1] https://ci.debian.net/packages/n/node-grunt-c
Source: node-is-glob
Version: 4.0.0-1
Severity: serious
Hi Maintainer
Upgrading node-is-glob to version 4.0.0 broke the following reverse
dependencies:
node-glob-base
node-glob-parent
node-parse-glob
As it can be seen in the debci logs [1][2][3], the failures all
started on 2017-12-15.
Regards
Control: block 894877 by -1
Is reverting to node-source-map 0.5.7 an option?
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Source: node-simple-swizzle
Version: 0.2.2-2
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic autopkgtest
Hi Maintainer
The --compilers option was deprecated [1] in recent versions of mocha.
This causes your package's autopkgtests to fail.
I have fixed this in the a
mocha/wiki/compilers-deprecation
+Author: Graham Inggs
+Last-Update: 2018-03-28
+
+--- a/test/mocha.opts
b/test/mocha.opts
+@@ -1,2 +1,2 @@
+---compilers coffee:coffee-script/register
++--require coffee-script/register
+ --reporter spec
--- a/debian/patches/series
+++ b/debian/patches/series
@@
Source: mapnik-reference
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic autopkgtest
Hi Maintainer
The quote escaping bug [1] was recently fixed in autopkgtest 5.2.
This means you can finally fix those crazy quotes, for example:
--- a/debian/tests/control
++
Source: node-stringprep
Version: 0.8.0-3
Tags: patch buster sid
Hi Jonas
While rebuilding node-stringprep for the nodejs-abi-57 in Ubuntu, it
FTBFS with a recent version of GCC. I found a pull request against
upstream's github which fixed the build and I have attached it here.
According to
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
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
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
I believe this is related to unreliable timing in tests being
discussed in #853035.
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
Source: node-once
Version: 1.4.0-2
Severity: serious
User: ci-t...@tracker.debian.org
Usertags: flaky
Hi Maintainer
Since the upload of nodejs 8.9.3, node-once has FTBFS [1] and
autopkgtests have been failing [2] with errors similar to the
following:
ok 1166 - should be equivalent
Source: node-tap
Version: 11.0.0+ds1-2
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic autopkgtest
User: ci-t...@package.debian.org
Usertags: flaky
Hi Maintainer
Since the upload of nodejs 8.9.3, node-tap has FTBFS [1] and
autopkgtests have been failing [2] wi
Source: node-commander
Version: 2.12.2-1
Severity: serious
Hi Maintainer
Since the upload of nodejs 8.9.3, node-commander has FTBFS [1] with
errors similar to the
following:
/usr/lib/nodejs/should/lib/assertion.js:72
throw new AssertionError(params);
^
AssertionError: expected '' to be '
For reference, I found similar timing issues and filed bugs for the
following packages:
node-foreground-child #894797
node-tap #895312
node-once #895316
node-commander #895317
In Ubuntu, we relaxed the timing of the failing tests until they
passed on all release architectures.
--
Pkg-javascript
31 matches
Mail list logo