Scala system tests

[peller]

No description provided.

[poplav]

One of the intermittent errors is the result of a compilation/interpreter error when invoking a function. As a setup to the tests we run all cells and ensure all finished executing in order to proceed to the actual tests of correct output. In this case the kernel will fail on cell five urth-core-bind where we invoke a simple function and fail to execute any other cells/reach the tests. The source is unknown whether widgets or toree.

[lbustelo]

@poplav And the error above cannot be replicated locally?

[poplav]

This error appears locally a very small percent of the time, but more frequently on travis. I think this error is hidden when run on travis, but explains why it will get stuck on a run all in travis (where we are logging the number of output areas/cells executed). This is a compiler/interpreter error when the function is invoked, which is very strange/not sure if this deals with toree.
There also is an intermittent issue I believe with the channel init message reaching the kernel on initial page load and init of widgets. If it is not inited by the time we invoke channel this.channel will be null as it hasn't been registered. This issue goes away though when the page is refreshed and the init channel message finally reaches the kernel. Making channel set lazy solved for the message arriving after a run all, but in this case it wouldn't arrive until you do a page refresh. Would the PR regarding require user to init change this behavior once it gets merged in?

[lbustelo]

@poplav now that the init code is part of master... can you try and rebase this branch and see if it start running reliably?