[debbugs-tracker] bug#37421: closed (node fails to build during update)

[GNU bug Tracking System]

Your message dated Fri, 20 Sep 2019 17:31:29 +0200
with message-id <87y2yjugq6.fsf@nckx>
and subject line Re: bug#37421: Apply nodejs test workaround?
has caused the debbugs.gnu.org bug report #37421,
regarding node fails to build during update
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
37421: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=37421
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: node fails to build during update Date: Mon, 16 Sep 2019 10:57:55 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)

Hi,

I'm trying to update ungoogled-chromium package but it fails on node
build and this happens repeatedly:

(guix pull done before)
$ guix package -u
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
building /gnu/store/vk49dlkkixsik0fw9gsmnqn4jmgfw099-node-10.15.3.drv...
| 'check' phasebuilder for 
`/gnu/store/vk49dlkkixsik0fw9gsmnqn4jmgfw099-node-10.15.3.drv' failed with exit 
code 1
build of /gnu/store/vk49dlkkixsik0fw9gsmnqn4jmgfw099-node-10.15.3.drv failed
View build log at 
'/var/log/guix/drvs/vk/49dlkkixsik0fw9gsmnqn4jmgfw099-node-10.15.3.drv.bz2'.
cannot build derivation 
`/gnu/store/n6h5fv4isjjnqchpjfb5m7cv765s3vi0-ungoogled-chromium-76.0.3809.132-0.8eba5c0.drv':
 1 dependencies couldn't be built
guix package: error: build of 
`/gnu/store/n6h5fv4isjjnqchpjfb5m7cv765s3vi0-ungoogled-chromium-76.0.3809.132-0.8eba5c0.drv'
 failed

I'm attaching log file from the build. 

49dlkkixsik0fw9gsmnqn4jmgfw099-node-10.15.3.drv.bz2
Description: Log file from failed node build

--
Thank you for your time!
sirmacik
PGP: 0xE0DC81D523891771

--- End Message ---

--- Begin Message --- Subject: Re: bug#37421: Apply nodejs test workaround? Date: Fri, 20 Sep 2019 17:31:29 +0200

Jack,

Jack Hill 写道：

I wanted to ping this issue. From the discussion in #37421, it seems like we are OK with disabling the problematic tests as a work-around

for now.

We are. Done as aae65db560bd146ba47774cca46056d72be2a5d4 and closing.

Kind regards,

T G-R

signature.asc
Description: PGP signature

--- End Message ---