Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TestWorkflowEnvironment schedules the first activity retry immediately #1069

Open
Tracked by #1094
nagl-stripe opened this issue Mar 10, 2022 · 0 comments
Open
Tracked by #1094
Labels
bug Something isn't working test server Related to the test server

Comments

@nagl-stripe
Copy link
Contributor

nagl-stripe commented Mar 10, 2022

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 nagl-stripe@b4f764d - 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
@Spikhalskiy Spikhalskiy mentioned this issue Mar 22, 2022
49 tasks
@Spikhalskiy Spikhalskiy added the bug Something isn't working label Apr 13, 2022
@sync-by-unito sync-by-unito bot added the test server Related to the test server label Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working test server Related to the test server
Projects
None yet
Development

No branches or pull requests

2 participants