Hi (Lincoln),
could you please describe the issue with forge resolver more closely?
I think I was hit by that few times - the app is behaving differently
when I build only one module, then run test with other, and in whole run.
What's the cause and what exactly does it cause - what should I count with?
On unrelated note - I changed few things, rebuilt few times, and now
instead of
HintsClassificationsTest.testIterationVariableResolving:162
expected:<3> but was:<0>
I have
HintsClassificationsTest.testIterationVariableResolving:162
expected:<3> but was:<4>
Which is good - the whole run sticks with the same graph :)
But a bit weirder - having more nodes than the test expects...
More tomorrow.
Ondra