Vagrant test VM not working

[igorbga]

I've been trying to run the tests for Aikau but with no success.

After running "mvn clean install jetty:run" in my local machine I can navigate without any issue to "http://localhost:8089/aikau/page/tp/ws/Index" and it shows the test page list as expected, so I don't think the trouble is there.

Then when I run "grunt test" the unit test screen appears but it does not progress, check the image here:

https://imagebin.ca/v/3A5T4HstmJZ4

I've logged to the Trusty virtual machine and even updated it (apt-get update, apt-get upgrade), but nothing changes.

Checking the logs i can see that whenever i try to run the test i get this in syslog:

Jan 25 09:37:31 vagrant-ubuntu-trusty-64 kernel: [ 113.224377] 770aaa1a3ea936b[2657]: segfault at 8 ip 0000000000453d87 sp 00007efd874c7070 error 4 in chromedriver[400000+503000]
Jan 25 09:37:40 vagrant-ubuntu-trusty-64 kernel: [ 122.483550] Chrome_ChildThr[2598]: segfault at 0 ip 00007fb1e4d2c0b7 sp 00007fb1d55fe410 error 6 in plugin-container[7fb1e4d23000+3d000]

[draperd]

Have you tried following the steps in this video: https://community.alfresco.com/videos/1050-how-to-setup-a-linux-developmenttest-environment-for-aikau

[igorbga]

I've installed Linux Mint 18.1 in a new VM and followed the instructions in the wiki and in the video.
Now I can confirm a similar behaviour as explained by AxelFaust in this other bug report:

#1185

When I run "grunt test_local" I get a message in the jetty server about "RequireEverything" file and in the terminal where I ran the "grunt test_local" just a blank screen. Node is taking the 100% o a single core and nothing else seems to happen.

[draperd]

OK... I have previously been unable to resolve this issue for Axel and I'm not sure I'm going to be able to do better now. I would recommend that rather than contributing this widget back to core Aikau it either remains in your own private namespaced package or you work with other community members to set up a community package distribution of widgets where the community manages contributions and testing themselves.

[igorbga]

Ok David.

The widget is already public in our git repository, changing the namespace is trivial, in fact I've already done so in order to progress with the project I'm currently working on. If a community package emerges I'l be happy to contribute it there too.

But to be honest, and with sincerely not any intention to offend, don't you think that not solving the testability makes contribution to Aikau almost imposible?

Is other people being able to test and contribute new widgets?

[draperd]

No offence taken. You are completely right, if it's not possible to test then people will not be able to contribute to Aikau.