I've tried with a trixie armel chroot, and indeed some tests time out. It's a common problem on slow architectures - the timeout value set in the test suite is often too short.
Le dim. 4 août 2024 à 12:05, Jérémy Lal <[email protected]> a écrit : > Cannot reproduce in a sid armel chroot on amdahl.debian.org. > > Le dim. 4 août 2024 à 10:37, Bastien Roucariès <[email protected]> a > écrit : > >> Hi, >> >> test fail on armel only >> >> See: >> https://ci.debian.net/packages/n/node-lru-cache/testing/armel/49749211/ >> https://ci.debian.net/packages/n/npm/testing/armel/49963003/ >> https://ci.debian.net/packages/n/node-tap-parser/testing/armel/49973906/ >> >> It seems it come from node-tap a pure javascript package, so failure may >> be in nodejs armel >> >> Do you have any idea how to debug >> >> Bastien > >
