Skip to content

Consolidating all Flaky Test issues into one single issue #1732

@siri-varma

Description

@siri-varma

Tracking: Flaky Tests and CI Reliability

This is a consolidated tracking issue for all known flaky test and CI reliability problems in the Java SDK. Flaky tests erode confidence in CI, slow down PR merges, and waste maintainer time on re-runs.

Related Issues

Issue Area Status
#725 Integration tests (general) Open
#1258 CI build step — dapr stop failure Open
#1321 Actor tests Open
#1367 Jobs tests (DaprJobsIT) Open
#1603 PubSub Outbox tests (DaprPubSubOutboxIT) Open

Problem Areas

1. Flaky Integration Tests (#725)

The original umbrella issue. Multiple integration tests have historically been unreliable, causing spurious CI failures across different test suites.

2. CI Build Step Failure — App Stop Race Condition (#1258)

The CI build sometimes fails because dapr stop is called on an app that has already exited. The error couldn't find app id causes the build step to fail even though the test itself passed. Failing to stop an already-exited app should not fail the build.

3. Flaky Actor Tests (#1321)

Actor integration tests intermittently fail in CI. Linked CI run: https://github.com/dapr/java-sdk/actions/runs/14605088504/job/40972206420?pr=1235

4. Flaky Jobs Test — DaprJobsIT.testJobScheduleCreationWithAllParameters (#1367)

This test fails intermittently with:

#1603
#1367
#1321
#1258
#725

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions