Fix durable task flaky integration test

[siri-varma]

Description

Fixes flaky Durable Task integration tests and adds a CI retry safety net so transient infrastructure hiccups don't fail otherwise-green runs.

Test fixes (DurableTaskClientIT)

longTimeStampTimer — The timer's fire time was computed from the test's wall clock at method start, and the test then asserted an exact internal sub-timer count (counter >= 4). The number of sub-timers a long timer is split into depends on the span from the orchestration's creation time to the deadline; worker startup + scheduling latency shrank that span under CI load, occasionally dropping a sub-timer and failing expected <true> but was <false>. Fix: anchor the timer to the orchestration's own replay-safe clock via ctx.getCurrentInstant() (what createTimer(Duration) does internally) so the span is always exactly delay, and assert the splitting invariant (counter >= 3) instead of a latency-sensitive exact count.

waitForInstanceStartThrowsException — Scheduling the instance on a background thread raced waitForInstanceStart: if the wait reached the sidecar first it failed with "no such instance exists"; if the schedule won, the worker started the instance within 2s and nothing was thrown. Fix: schedule with a future start time so the instance deterministically exists but stays Pending, guaranteeing waitForInstanceStart blocks to its 2s deadline and throws TimeoutException.

CI retries (build.yml, validate.yml)

Wrap the flaky integration/validation commands in nick-fields/retry@v3 (max_attempts: 2, timeout_minutes: 30) at job granularity:

• Durable Task — retry the mvnw ... verify step; continue_on_error keeps the sidecar-log upload and the outcome-gated fail step intact.
• Spring Boot 3.5 / 4.0 build legs — retry the integration-test command; continue_on_error is left off so an exhausted retry still fails the step, preserving the existing failure() artifact uploads and job-failure behavior.
• Auto Validate — a single retry around all example validations (reruns the batch once on failure) rather than per-example.

Retries are a safety net for transient failures (sidecar/gRPC connect races, example runs), not a substitute for the root-cause test fixes above.

Issue reference

[add issue number if this closes one]

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Extended the documentation

[siri-varma]

@javier-aliaga durable task has a flaky test. Fixed it as part of this PR

[siri-varma]

nvm. It failed again

[siri-varma]

@javier-aliaga need one review on this pr please

[Copilot]

Pull request overview

This PR reduces flakiness in Durable Task integration tests by anchoring timer behavior to the orchestration’s replay-safe clock and making a timeout-based test deterministic, and it adds a CI retry wrapper around selected flaky integration/validation commands.

Changes:

• Update DurableTaskClientIT to compute timestamp timers from ctx.getCurrentInstant() and relax assertions to invariant-based checks.
• Make waitForInstanceStartThrowsException deterministic by scheduling an instance with a future start time and asserting TimeoutException.
• Wrap Durable Task integration tests, Spring Boot integration tests, and example validations in nick-fields/retry@v3 to reduce transient CI failures.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
durabletask-client/src/test/java/io/dapr/durabletask/DurableTaskClientIT.java	Fixes two flaky Durable Task integration tests by removing timing races and using orchestration time.
.github/workflows/validate.yml	Consolidates example validations into a single retried step to mitigate transient failures.
.github/workflows/build.yml	Adds retries around integration test steps and adjusts failure gating logic for Durable Task tests.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.02%. Comparing base (26b2327) to head (006f4db).

Additional details and impacted files

@@            Coverage Diff            @@
##             master    #1784   +/-   ##
=========================================
  Coverage     77.02%   77.02%           
  Complexity     2324     2324           
=========================================
  Files           245      245           
  Lines          7198     7198           
  Branches        760      760           
=========================================
  Hits           5544     5544           
  Misses         1288     1288           
  Partials        366      366           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.