I know there have been flaky tests in the past due to testing akka actors and dealing with the concurrency for those classes. My best guess is that current issues relate to similar timing issues.
It might be worth having some record of all the test runs so we can see which ones are consistently. Anybody know of a way to do this with travis? It basically would entail publishing the test report to some static host. On Fri, Mar 17, 2017 at 8:18 PM Luciano Resende <luckbr1...@gmail.com> wrote: > The current CI builds seems a little flaky, and will usually fail unrelated > to the changes being proposed. Has anyone investigated these issues and has > an understanding of what causes them? Is it related to Travis.CI? The > actual tests? Timing? > > Anyway, we should make the CI build more stable. > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ >
