Help Needed: Problem Building Node.js Package for i386 on Guix

Help Needed: Problem Building Node.js Package for i386 on Guix

[Yasindu Dissanayake]

[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]

Dear Guix Developers,

I hope you’re doing well. My name is Yasindu Dissanayake, and I’m working
on building a Node.js package for the i386 architecture in the MetaCall
project. I’ve run into an issue where some tests don’t work. I’ve tried
several fixes, like changing the package or even removing the test phase
completely, but nothing has worked so far.
DetailsHere’s the file I’m using:

metacall.scm - Line 83
<https://github.com/metacall/distributable-linux/blob/768eae41c72ee1ef5602325b175edad096ae3e5d/source/metacall.scm#L83>

This is a change I tried to make:
Commit: Removed Specific Tests
<https://github.com/metacall/distributable-linux/commit/cdc8d64b72e4ac4391d5311e3f76f9fd588781e3>

I’ve attached the build logs as a text file and also linked a CI run from
GitHub Actions for more details:
GitHub Actions CI Run
<https://github.com/metacall/distributable-linux/actions/runs/11619204193/job/32358306124>
Request

Could you please help me with the following?

   1. How can I debug these kinds of issues more effectively?
   2. Is there a common way to handle test problems for specific
   architectures in Guix?
   3. Do you see anything obvious I might be missing?

Thank you very much for your help. Let me know if you need more details.

Best regards,
Yasindu Dissanayake

[-- Attachment #2: logs.txt --]
[-- Type: text/plain, Size: 4413 bytes --]

ok 3733 known_issues/test-dgram-bind-shared-ports-after-port-0
  ---
  duration_ms: 607.59200
  ...
ok 3734 known_issues/test-fs-writeFileSync-invalid-windows
  ---
  duration_ms: 210.02000
  ...
ok 3735 known_issues/test-http-path-contains-unicode
  ---
  duration_ms: 209.70400
  ...
ok 3736 known_issues/test-http2-trailers-after-session-close
  ---
  duration_ms: 261.52500
  ...
ok 3737 known_issues/test-inspector-cluster-port-clash
  ---
  duration_ms: 507.47200
  ...
ok 3738 known_issues/test-repl-require-context
  ---
  duration_ms: 261.67500
  ...
ok 3739 known_issues/test-stdin-is-always-net.socket
  ---
  duration_ms: 407.18900
  ...
ok 3740 known_issues/test-stream-writable-sync-error
  ---
  duration_ms: 209.72900
  ...
ok 3741 known_issues/test-url-parse-conformance
  ---
  duration_ms: 261.64200
  ...
ok 3742 known_issues/test-vm-function-declaration-uses-define
  ---
  duration_ms: 209.75400
  ...
ok 3743 known_issues/test-vm-ownkeys
  ---
  duration_ms: 209.79100
  ...
ok 3744 known_issues/test-vm-ownpropertynames
  ---
  duration_ms: 209.80700
  ...
ok 3745 known_issues/test-vm-ownpropertysymbols
  ---
  duration_ms: 209.63600
  ...
ok 3746 known_issues/test-vm-timeout-escape-nexttick
  ---
  duration_ms: 908.49000
  ...
ok 3747 wpt/test-abort
  ---
  duration_ms: 2511.19800
  ...
ok 3748 wpt/test-atob
  ---
  duration_ms: 326.35200
  ...
ok 3749 wpt/test-blob
  ---
  duration_ms: 707.98500
  ...
ok 3750 wpt/test-broadcastchannel
  ---
  duration_ms: 507.60200
  ...
ok 3751 wpt/test-console
  ---
  duration_ms: 708.16400
  ...
ok 3752 wpt/test-domexception
  ---
  duration_ms: 607.60000
  ...
ok 3753 wpt/test-encoding
  ---
  duration_ms: 3113.66900
  ...
ok 3754 wpt/test-events
  ---
  duration_ms: 908.67700
  ...
ok 3755 wpt/test-file
  ---
  duration_ms: 326.72800
  ...
ok 3756 wpt/test-hr-time
  ---
  duration_ms: 2511.38700
  ...
ok 3757 wpt/test-microtask-queuing
  ---
  duration_ms: 261.97400
  ...
ok 3758 wpt/test-performance-timeline
  ---
  duration_ms: 4815.63000
  ...
ok 3759 wpt/test-streams
  ---
  duration_ms: 8321.86400
  ...
ok 3760 wpt/test-structured-clone
  ---
  duration_ms: 407.67300
  ...
ok 3761 wpt/test-timers
  ---
  duration_ms: 708.02000
  ...
ok 3762 wpt/test-url
  ---
  duration_ms: 3014.27500
  ...
ok 3763 wpt/test-user-timing # TODO : Fix flaky test
  ---
  duration_ms: 1809.96700
  ...
ok 3764 wpt/test-wasm-webapi
  ---
  duration_ms: 1109.64700
  ...
ok 3765 wpt/test-webcrypto
  ---
  duration_ms: 247748.00400
  ...
ok 3766 abort/test-abort-backtrace
  ---
  duration_ms: 510.73000
  ...
ok 3767 abort/test-abort-fatal-error
  ---
  duration_ms: 610.49100
  ...
ok 3768 abort/test-abort-uncaught-exception
  ---
  duration_ms: 611.26700
  ...
ok 3769 abort/test-addon-register-signal-handler # skip binding not built yet
  ---
  duration_ms: 213.21100
  ...
ok 3770 abort/test-addon-uv-handle-leak # skip binding not built yet
  ---
  duration_ms: 213.04100
  ...
ok 3771 abort/test-http-parser-consume
  ---
  duration_ms: 610.48300
  ...
ok 3772 abort/test-process-abort-exitcode
  ---
  duration_ms: 510.37500
  ...
ok 3773 abort/test-signal-handler
  ---
  duration_ms: 510.48400
  ...
ok 3774 abort/test-worker-abort-uncaught-exception
  ---
  duration_ms: 610.63000
  ...
ok 3775 abort/test-zlib-invalid-internals-usage
  ---
  duration_ms: 510.13200
  ...

Failed tests:
out/Release/node /tmp/guix-build-libnode-18.19.0.drv-0/node-v18.19.0/test/parallel/test-fs-utimes-y2K38.js
make: *** [Makefile:539: test-ci-js] Error 1

Test suite failed, dumping logs.
error: in phase 'check': uncaught exception:
%exception #<&invoke-error program: "make" arguments: ("test-ci-js" "-j" "4") exit-status: 2 term-signal: #f stop-signal: #f> 
phase `check' failed after 1293.3 seconds
command "make" "test-ci-js" "-j" "4" failed with status 2
build process 6 exited with status 256
builder for `/gnu/store/kw84dhvgykxlf5pqfg032pyfwm5kdgxa-libnode-18.19.0.drv' failed with exit code 1
build of /gnu/store/kw84dhvgykxlf5pqfg032pyfwm5kdgxa-libnode-18.19.0.drv failed
View build log at '/var/log/guix/drvs/kw/84dhvgykxlf5pqfg032pyfwm5kdgxa-libnode-18.19.0.drv.gz'.
cannot build derivation `/gnu/store/wxpcniry63jm44dk58jxak177541g8kj-metacall-0.8.1.drv': 1 dependencies couldn't be built
guix build: error: build of `/gnu/store/wxpcniry63jm44dk58jxak177541g8kj-metacall-0.8.1.drv' failed
Error: Process completed with exit code 1.