chess.ClockTest failing

[Seth Tisue]

in the context of the Scala community build, I started seeing this failure happening (every run, not just intermittently):

[scalachess] [info]   multiple premoves with fast clock
[scalachess] [info]     + no lag
[scalachess] [error]     x no -> medium lag
[scalachess] [error]      5948 != 5932 (ClockTest.scala:122)
[scalachess] [error]     x no x4 -> big lag
[scalachess] [error]      5672 != 5648 (ClockTest.scala:125)

see e.g. the log at https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/2327/consoleFull

for now I have dealt with it by freezing scalachess at revision a1c8abe, before the regression was introduced, but it would be nice if we could go back to tracking your master branch

[Niklas Fiekas]

@isaacl Probably just some changed expectations after e88195d?

[Thibault Duplessis]

Looks like we need better alerting for failed builds https://travis-ci.org/ornicar/scalachess

[Isaac Levy]

Yeah just need to set expectations again. Sorry

[Seth Tisue]

unfrozen in community build: scala/community-build@829911b