Skip to content

Flaky StreamReliability restart test reports duplicate publisher registration #10907

Description

@ReubenBond

The aggregate .NET Test Results check reported one failure out of 54,077 tests in the Azure Storage net8 job:

UnitTests.Streaming.Reliability.StreamReliabilityTests.SMS_StreamRel_AllSilosRestart_PubSubCounts

Observed failure:

After SendItem - PublisherCount for stream MemoryStreamProvider/StreamReliabilityNamespace/7176ccad648b4af6849d1a332ef378d6 = 2; expected 1; provider=MemoryStreamProvider; namespace=StreamReliabilityNamespace

Stack:

StreamTestUtils.CheckPubSubCount at test/Orleans.Streaming.Tests/StreamingTests/StreamTestUtils.cs:87
StreamReliabilityTests.Test_AllSilosRestart_PubSubCounts at test/Extensions/Orleans.Azure.Tests/Streaming/StreamReliabilityTests.cs:760
StreamReliabilityTests.SMS_StreamRel_AllSilosRestart_PubSubCounts at test/Extensions/Orleans.Azure.Tests/Streaming/StreamReliabilityTests.cs:272

The individual Azure Storage net8 job otherwise completed, all other CI test jobs passed, and searches found no existing issue or PR for this exact failure. The restart path appears to retain or re-register a publisher so the post-restart pub/sub count becomes 2 instead of 1.

Check run: 98863181863; source workflow run: 33173664750.

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