Skip to content

Remove flaky check from StateFlowStressTest. #4483

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

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

chaoren
Copy link
Contributor

@chaoren chaoren commented Jul 18, 2025

There's no guarantee that any particular collector will ever encounter a value emitted by a particular emitter. It's entirely possible for the value to be overwritten by a different emitter before the collector gets a chance to collect it. It's very, very unlikely for a collector to miss the second half of all values emitted by a particular emitter, but it is possible to happen and this causes the test to be flaky.

There's no guarantee that any particular collector will ever encounter
a value emitted by a particular emitter. It's entirely possible for the
value to be overwritten by a different emitter before the collector gets
a chance to collect it. It's very, very unlikely for a collector to miss
the second half of all values emitted by a particular emitter, but it
is possible to happen and this causes the test to be flaky.
@chaoren
Copy link
Contributor Author

chaoren commented Jul 18, 2025

I guess if you want to check that none of the collectors "hanged up" then you could check that c.max() is sufficiently high?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant