Source: node-webpack
Version: 5.97.1+dfsg1+~cs11.18.27-1
Severity: important
Tags: ftbfs

The test suite segfaults on riscv64, on every run.

Reproducible @ricci.debian.org.

Is not a problem with jest (and its snapshots), as it segfaults too with mocha/expect.js.

Not sure the backtrace makes sense, though:

#3 0x0000003ff4d07d50 in pthread_cond_timedwait () from /lib/riscv64-linux-gnu/libc.so.6
#4 0x0000003ff6540bb2 in v8::base::ConditionVariable::WaitFor(v8::base::Mutex*, v8::base::TimeDelta const&) () from /lib/riscv64-linux-gnu/libnode.so.115
#5 0x0000003ff61d5bb0 in v8::internal::SamplingEventsProcessor::Run() () from /lib/riscv64-linux-gnu/libnode.so.115


The test suite is very long, and each independent test pass.

It fails only when all tests are run (sequentially or in parallel),
so I suppose something is overflowing, somewhere.



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

Kernel: Linux 6.12.19-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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Le ven. 21 mars 2025 à 13:45, Jérémy Lal <kapouer@melix.org> a écrit :

Source: node-webpack
Version: 5.97.1+dfsg1+~cs11.18.27-1
Severity: important
Tags: ftbfs

The test suite segfaults on riscv64, on every run.

Reproducible @ricci.debian.org.

Is not a problem with jest (and its snapshots), as it segfaults too with mocha/expect.js.

Not sure the backtrace makes sense, though:

#3 0x0000003ff4d07d50 in pthread_cond_timedwait () from /lib/riscv64-linux-gnu/libc.so.6
#4 0x0000003ff6540bb2 in v8::base::ConditionVariable::WaitFor(v8::base::Mutex*, v8::base::TimeDelta const&) () from /lib/riscv64-linux-gnu/libnode.so.115
#5 0x0000003ff61d5bb0 in v8::internal::SamplingEventsProcessor::Run() () from /lib/riscv64-linux-gnu/libnode.so.115

The test suite is very long, and each independent test pass.

I overlooked one of the tests: ProfilingPlugin.unittest.js
CPU Profiler is known to fail on RISCV64.

Jérémy

<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">Le ven. 21 mars 2025 à 13:45, Jérémy Lal &lt;<a href="mailto:kapouer@melix.org">kapouer@melix.org</a>&gt; a écrit :<br></

<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Source: node-webpack<br>

Version: 5.97.1+dfsg1+~cs11.18.27-1<br>
Severity: important<br>
Tags: ftbfs<br>

The test suite segfaults on riscv64, on every run.<br>

Reproducible @<a href="http://ricci.debian.org" rel="noreferrer" target="_blank">ricci.debian.org</a>.<br>

Is not a problem with jest (and its snapshots), as it segfaults too with mocha/expect.js.<br>

Not sure the backtrace makes sense, though:<br>

#3  0x0000003ff4d07d50 in pthread_cond_timedwait () from /lib/riscv64-linux-gnu/libc.so.6<br>
#4  0x0000003ff6540bb2 in v8::base::ConditionVariable::WaitFor(v8::base::Mutex*, v8::base::TimeDelta const&amp;) () from /lib/riscv64-linux-gnu/libnode.so.115<br>
#5  0x0000003ff61d5bb0 in v8::internal::SamplingEventsProcessor::Run() () from /lib/riscv64-linux-gnu/libnode.so.115<br>


The test suite is very long, and each independent test pass.<br></blockquote><div><br></div><div>I overlooked one of the tests: ProfilingPlugin.unittest.js</div><div>CPU Profiler is known to fail on RISCV64.</div><div><br></div><div>Jérémy</div></div><
/div>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)