hard timeouts are being reached

[lightbend-labs]

hard timeouts are being reached

[cunei]

The hard timeouts are fixed in recent commits: beginning with version 0.9.10 all the timeouts can be freely configured (and are properly captured)

[gkossakowski]

On related note: this nicely shows that there's little hope for this to be run every PR. I personally don't think it's necessary. The bigger problem will be once we hit 24h limit and dbuild won't be able to catch up on nightly basis.

[cunei]

No, unexpected means really unexpected; that particular timeout should only be reached if there is a bug somewhere in the code. If all works as expected, the relevant timeout is this one:

  val extractionPlusBuildTimeout: Timeout = 5.hours

It seems really slow; it takes less than half that time on my local machine. Aside from the cpu difference, the resolution time might impact quite a bit. I need to add artifactory to that system; right now I'm trying to cut a new dbuild release, but I'll be on it asap next week.

There is not enough time to make those timeouts parametric and adding per-project timings in time for this particular release, but I'll add these features to the next point release. In the meantime, I'll bump up the timeouts substantially.

[retronym]

Thanks for the explanation, Toni.

Obviously we'd prefer to speed up the build; really looking forward to the proxy.