TestWorkflowEnvironment schedules the first activity retry immediately

Expected Behavior

With a retry policy like:

      RetryOptions.newBuilder()
          .setInitialInterval(Duration.ofSeconds(10))
          .setBackoffCoefficient(2.0)
          .build();

I would expect delays of 10, 20, 40, 80, so attempts (including the first one) run at T0, 10, 30, 70, 150.

Actual Behavior

Attempts run at T0, 0, 10, 30, 70 - the first retry gets scheduled immediately.

Steps to Reproduce the Problem

Check out https://github.com/nagl-stripe/sdk-java/commit/b4f764dfdc22102893be1916b325a40322ccd54e - it has a test case that would pass if the actual behavior were the expected behavior

This is very much not-urgent =)

Specifications

• Version: latest
• Platform: TestWorkflowEnviornment

Commencez par le cas de test du commit b4f764dfdc22102893be1916b325a40322ccd54e et examinez comment TestWorkflowEnvironment planifie les nouvelles tentatives des activities. Reproduisez la stratégie de nouvelle tentative avec des délais de 10, 20, 40 et 80 secondes, puis vérifiez que les tentatives ont lieu à T0, 10, 30, 70 et 150, au lieu de réessayer immédiatement.