just FYI: using the exact parameters of the failing test (randomly generated), I was able to reproduce this now locally - so we should be able to fix this flaky test once and for all.
Regards, Matthias On Wed, Sep 20, 2017 at 2:21 PM, <jenk...@spark.tc> wrote: > See <https://sparktc.ibmcloud.com/jenkins/job/SystemML-DailyTest/1247/> > >
