Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.rc > #324062 > unrolled thread

Bug#1016305: nodejs: FTBFS: make[2]: *** [Makefile:504: test-ci-js] Error 1

Back to article view | Back to linux.debian.bugs.rc

Contents

  Bug#1016305: nodejs: FTBFS: make[2]: *** [Makefile:504: test-ci-js] Error 1 Lucas Nussbaum <lucas@debian.org> - 2022-07-29 20:30 +0200
    Bug#1016305: nodejs: FTBFS: make[2]: *** [Makefile:504: test-ci-js] Error 1 Jérémy Lal <kapouer@melix.org> - 2022-07-30 17:30 +0200
    Bug#1016305: nodejs: FTBFS: make[2]: *** [Makefile:504: test-ci-js] Error 1 Jérémy Lal <kapouer@melix.org> - 2022-07-31 16:40 +0200
    Bug#1016305: marked as done (nodejs: FTBFS: make[2]: ***  [Makefile:504: test-ci-js] Error 1) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-08-01 23:00 +0200

#324062 — Bug#1016305: nodejs: FTBFS: make[2]: *** [Makefile:504: test-ci-js] Error 1

Source: nodejs
Version: 18.6.0+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20220728 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> not ok 1778 parallel/test-net-socket-connect-without-cb
>   ---
>   duration_ms: 0.261
>   severity: fail
>   exitcode: 1
>   stack: |-
>     node:events:491
>           throw er; // Unhandled 'error' event
>           ^
>     
>     Error: getaddrinfo EAI_AGAIN localhost
>         at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:111:26)
>     Emitted 'error' event on Socket instance at:
>         at emitErrorNT (node:internal/streams/destroy:151:8)
>         at emitErrorCloseNT (node:internal/streams/destroy:116:3)
>         at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
>       errno: -3001,
>       code: 'EAI_AGAIN',
>       syscall: 'getaddrinfo',
>       hostname: 'localhost'
>     }
>     
>     Node.js v18.6.0
>   ...
[...]
> not ok 2130 parallel/test-socket-write-after-fin-error
>   ---
>   duration_ms: 0.327
>   severity: fail
>   exitcode: 1
>   stack: |-
>     node:assert:400
>         throw err;
>         ^
>     
>     AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value:
>     
>       assert(gotServerError)
>     
>         at process.<anonymous> (/<<PKGBUILDDIR>>/test/parallel/test-socket-write-after-fin-error.js:52:5)
>         at process.emit (node:events:525:35) {
>       generatedMessage: true,
>       code: 'ERR_ASSERTION',
>       actual: false,
>       expected: true,
>       operator: '=='
>     }
>     
>     Node.js v18.6.0
>   ...
[...]
> not ok 2576 parallel/test-tls-streamwrap-buffersize
>   ---
>   duration_ms: 0.326
>   severity: fail
>   exitcode: 1
>   stack: |-
>     Mismatched <anonymous> function calls. Expected exactly 1, actual 0.
>         at Proxy.mustCall (/<<PKGBUILDDIR>>/test/common/index.js:392:10)
>         at TLSSocket.<anonymous> (/<<PKGBUILDDIR>>/test/parallel/test-tls-streamwrap-buffersize.js:63:35)
>         at TLSSocket.<anonymous> (/<<PKGBUILDDIR>>/test/common/index.js:434:15)
>         at Object.onceWrapper (node:events:627:28)
>         at TLSSocket.emit (node:events:513:28)
>         at TLSSocket.onConnectSecure (node:_tls_wrap:1567:10)
>         at TLSSocket.emit (node:events:513:28)
>         at TLSSocket._finishInit (node:_tls_wrap:948:8)
>         at ssl.onhandshakedone (node:_tls_wrap:729:12)
>   ...
[..]
> not ok 3072 sequential/test-debugger-preserve-breaks # TODO : Fix flaky test
>   ---
>   duration_ms: 31.166
>   severity: flaky
>   exitcode: 1
>   stack: |-
>     /<<PKGBUILDDIR>>/test/common/debugger.js:84
>               reject(new Error([
>                      ^
>     
>     Error: Timeout (30000) while waiting for /(?:assert|break|break on start|debugCommand|exception|other|promiseRejection) in/i; found: debug> 
>     debug> 
>     
>     < Waiting for the debugger to disconnect...
>     < 
>     
>     debug> 
>         at Timeout.<anonymous> (/<<PKGBUILDDIR>>/test/common/debugger.js:84:18)
>         at listOnTimeout (node:internal/timers:564:17)
>         at process.processTimers (node:internal/timers:507:7)
>     
>     Node.js v18.6.0
>   ...

The full build log is available from:
http://qa-logs.debian.net/2022/07/28/nodejs_18.6.0+dfsg-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lucas@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220728&fusertaguser=lucas@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

[toc] | [next] | [standalone]

#324156

Source: nodejs
Version: 18.6.0+dfsg-3
Followup-For: Bug #1016305
X-Debbugs-Cc: libuv1@packages.debian.org

The two actually failing tests are:
parallel/test-socket-write-after-fin-error
parallel/test-tls-streamwrap-buffersize

Those failures are regressions caused by recent upload of libuv1 1.44.2.

Upstream nodejs already knows this but they are still
figuring out how to fix one of the failures.

libuv1 maintainer: please avoid uploading new versions when nodejs is
in transition...


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

[toc] | [prev] | [next] | [standalone]

#324262

[Multipart message — attachments visible in raw view] — view raw

Le dim. 31 juil. 2022 à 16:27, Dominique Dumont <domi.dumont@free.fr> a
écrit :

> On Saturday, 30 July 2022 19:36:26 CEST you wrote:
> > libuv1 is a library, you're supposed to manage the transition:
> > https://wiki.debian.org/Teams/ReleaseTeam/Transitions
>
> This page applies when the new version breaks the ABI or API. This was not
> the
> case. There was no symbol change. The SO version of libuv1 has not changed
> since the transition between libuv and libuv1.
>

Indeed, sorry for my somewhat irritated tone - it just happens that it was
the second time
libuv1 was updated during a nodejs transition, and the upstream bug it
creates on nodejs
hasn't been fixed yet, so it shoots the transition in the guts.
Nodejs depends heavily on libuv1...

> In particular, rebuild all reverse build dependencies and check they
> won't
> break is highly desirable.
> > There are tools and services in debian to do that (though honestly it's
> not
> so easy to setup).
>
> I'm already stretched quite thin. I'll see what I can do.
>
> In any case, I'd be happy to handover libuv1 to people willing to better
> maintain this package.


Maybe a simple approach would be to upload libuv1 updates to experimental
first,
and wait a week to see how it scares the others :)

Jérémy
Jérémy

[toc] | [prev] | [next] | [standalone]

#324344 — Bug#1016305: marked as done (nodejs: FTBFS: make[2]: *** [Makefile:504: test-ci-js] Error 1)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Mon, 01 Aug 2022 20:50:48 +0000
with message-id <E1oIcNE-007TN2-Pv@fasolo.debian.org>
and subject line Bug#1016305: fixed in nodejs 18.6.0+dfsg-4
has caused the Debian Bug report #1016305,
regarding nodejs: FTBFS: make[2]: *** [Makefile:504: test-ci-js] Error 1
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 owner@bugs.debian.org
immediately.)


-- 
1016305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016305
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.rc

csiph-web