Bug#956238: npm: autopkgtest failures in arm64 and ppc64el

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#956238: npm: autopkgtest failures in arm64 and ppc64el

Gianfranco Costamagna via nm
Source: npm
Version: 6.13.4+ds-2
Severity: serious

Hello, looks like probably since version 6.x, a new autopkgtest introduced has been failing on arm64, ppc64el and s390x (this one happens in Ubuntu, but should be reproducible in Debian too).

https://ci.debian.net/packages/n/npm/unstable/arm64/
https://ci.debian.net/packages/n/npm/unstable/ppc64el/

Can you please have a look?

thanks

Gianfranco

Reply | Threaded
Open this post in threaded view
|

Bug#956238: [Pkg-javascript-devel] Bug#956238: npm: autopkgtest failures in arm64 and ppc64el

Xavier Guimard-3
Control: severity -1 important

Le 08/04/2020 à 20:18, Gianfranco Costamagna a écrit :

> Source: npm
> Version: 6.13.4+ds-2
> Severity: serious
>
> Hello, looks like probably since version 6.x, a new autopkgtest introduced has been failing on arm64, ppc64el and s390x (this one happens in Ubuntu, but should be reproducible in Debian too).
>
> https://ci.debian.net/packages/n/npm/unstable/arm64/
> https://ci.debian.net/packages/n/npm/unstable/ppc64el/
>
> Can you please have a look?
>
> thanks
>
> Gianfranco

Hi,

the problem is "address already in use :::56443". It's difficult to
enable network tests without reserved port on debci machines.

So it's not a really a bug

Reply | Threaded
Open this post in threaded view
|

Processed: Re: [Pkg-javascript-devel] Bug#956238: npm: autopkgtest failures in arm64 and ppc64el

Debian Bug Tracking System
In reply to this post by Gianfranco Costamagna via nm
Processing control commands:

> severity -1 important
Bug #956238 [src:npm] npm: autopkgtest failures in arm64 and ppc64el
Severity set to 'important' from 'serious'

--
956238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956238
Debian Bug Tracking System
Contact [hidden email] with problems