e.g. http://department.st.ewi.tudelft.nl/weblab/assignment/1192

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

On 24 January 2014 at 10:13 Elmer van Chastelet tagged 43

On 24 January 2014 at 10:23 Vlad Vergu commented:

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?


On 24 January 2014 at 10:31 Elmer van Chastelet commented:

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.


On 3 February 2014 at 17:34 Elmer van Chastelet removed tag 43

On 3 February 2014 at 17:34 Elmer van Chastelet tagged 41

On 17 February 2014 at 11:16 Elmer van Chastelet commented:

http://allievi.sssup.it/techblog/archives/798#comment-865187747

I just tested changing from -O0 --typed-arrays 0 to -O2 -s ASM_JS=1, and it runs fine. Hopefully this speeds things up :).

Edit: Does not run fine.


On 17 October 2014 at 16:30 Elmer van Chastelet removed tag 41

On 17 October 2014 at 16:30 Elmer van Chastelet tagged 42

On 5 November 2014 at 12:25 Elmer van Chastelet removed tag 42

On 5 November 2014 at 12:25 Elmer van Chastelet tagged 43

On 6 January 2015 at 15:38 Elmer van Chastelet tagged 49

On 6 January 2015 at 15:38 Elmer van Chastelet removed tag 43

Log in to post comments