Timeout when running some c tests
So compilation speed is OK, but running the tests takes too long.
Probably since emscripten update in which we also updated node.js, although I’m not completely sure if node.js is used by labback. Needs investigation.
Temporary quick fix would be to increase run-timeout in backend config, but we need a better solution.Submitted by Elmer van Chastelet on 24 January 2014 at 10:13
Labback does not use NodeJS. It uses the Mozilla Rhino JS interpreter. Maybe test running has gotten a lot slower because we turned off optimisations in Emscripten?
That might indeed be causing this. Sad to see that the server cpus are significantly slower in processing the js-code than my workstation cpus. I’ll have a look if speed can be improved.
ps. rhino lib was also updated with the emscripten update.
I just tested changing from
-O0 --typed-arrays 0to
-O2 -s ASM_JS=1,
and it runs fine. Hopefully this speeds things up :).
Edit: Does not run fine.
Log in to post comments