double timeout on flaky test

[pjfanning]

see #216

[raboof]

I wonder if we already set pekko.test.timefactor for GitHub Actions builds (https://pekko.apache.org/docs/pekko/current/general/configuration-reference.html#pekko-testkit), but this is OK in any case.

[pjfanning]

The same flaky test failed even with the timefactor=2 - but the timefactor didn't seem to increase the timeout - it still looks like the same same short 1.5 second timeout.

[info] - should be able to be created *** FAILED *** (1 second, 459 milliseconds)
[info]   The future returned an exception of type: org.apache.pekko.coordination.lease.LeaseTimeoutException, with message: Timed out removing lease [lease-1]. It is not known if the remove happened. Is the API server up?. (KubernetesApiSpec.scala:104)
[info]   org.scalatest.exceptions.TestFailedException:

[raboof]

hmm, maybe because this test explicitly sets it to testKitSettings.DefaultTimeout.duration? What happens when we remove that? sorry for leading you down this rabbit hole :/

[pjfanning]

Without the explicit patience config, things get far worse. All the individual scenarios timeout in 150ms (each).

[pjfanning]

I'll merge the original change that just doubles the time on the patience config in this test class.