action #109638
closed
- Related to action #107857: Enable and fix BCI tests on aarch64 (except dotnet family) added
Reson to do so:
6 test runs for NodeJS all failing with Error: Timeout of 2000ms exceeded
in the express
test repo - See the 4.51_nodejs-16-image build:
To be sure that this is a timeout due to missing computational resources, I performed the following tests:
- Use the
registry.suse.com/bci/nodejs:16
container on my RPi VM and run the express test: PASSING
- Use the
registry.suse.com/bci/nodejs:16
container on my emulated aarch64 VM and run the express test: FAIL (timeout)
The test procedure was
git clone https://github.com/expressjs/express.git
cd express
npm config set shrinkwrap false && npm rm --silent --save-dev connect-redis && npm run test-ci && npm run lint
To me it looks very much like a timeout due to a too tight timeout because our aarch64 openQA workers are not fast enough.
The error happens when running npm run test-ci
:
1) Router
should not stack overflow with many registered routes:
Error: Timeout of 2000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/opt/express/test/Router.js)
at /opt/express/test/Router.js:73:11
at Layer.handle [as handle_request] (lib/router/layer.js:35:103)
at next (lib/router/route.js:36:802)
at Route.dispatch (lib/router/route.js:34:677)
at Layer.handle [as handle_request] (lib/router/layer.js:35:103)
at /opt/express/lib/router/index.js:82:415
at Function.process_params (lib/router/index.js:93:170)
at next (lib/router/index.js:82:31)
at Function.handle (lib/router/index.js:67:194)
at Context.<anonymous> (test/Router.js:76:12)
at processImmediate (node:internal/timers:464:21)
It points nicely to test/Router.js:73:11
Full log: http://pasta.qam.suse.de/VxYTqXFr
After fixing npm
on aarch64, I think this ticket is no longer required?
- Status changed from Workable to Resolved
Also available in: Atom
PDF