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

racy spec fix: BackoffOnRestartSupervisor_must_respect_maxNrOfRetries_property_of_OneForOneStrategy #5442

Merged

Conversation

Aaronontheweb
Copy link
Member

issue was that using AutoReset could cause a race where if the scheduler could reset the count in-flight and throw off the estimates used by the tests. Using a ManualReset avoids this issue.

…s_property_of_OneForOneStrategy`

issue was that using `AutoReset` could cause a race where if the scheduler could reset the count in-flight and throw off the estimates used by the tests. Using a `ManualReset` avoids this issue.
@Aaronontheweb
Copy link
Member Author

Akka.Tests.Actor.ReceiveTimeoutSpec.An_actor_with_receive_timeout_must_get_timeout_while_receiving_NotInfluenceReceiveTimeout_messages - this is the test I'm working on fixing next.

@Aaronontheweb Aaronontheweb merged commit 60807fe into akkadotnet:dev Dec 17, 2021
@Aaronontheweb Aaronontheweb deleted the fix/RacySpec-BackoffOnRestart branch December 17, 2021 18:23
Aaronontheweb added a commit to Aaronontheweb/akka.net that referenced this pull request Dec 20, 2021
…s_property_of_OneForOneStrategy` (akkadotnet#5442)

issue was that using `AutoReset` could cause a race where if the scheduler could reset the count in-flight and throw off the estimates used by the tests. Using a `ManualReset` avoids this issue.
Aaronontheweb added a commit that referenced this pull request Dec 20, 2021
)

* remove the forced waiting on the underlying transport to start up

* racy spec fix: `BackoffOnRestartSupervisor_must_respect_maxNrOfRetries_property_of_OneForOneStrategy` (#5442)

issue was that using `AutoReset` could cause a race where if the scheduler could reset the count in-flight and throw off the estimates used by the tests. Using a `ManualReset` avoids this issue.

* deleted commented out code

* Make updates to `FishUntil` (#5433)

* Make updates to `FishUntil`

Implement nitpicks from #5430

* Nitpick

* cleaned up `FishUntilMessage`

* removed `FluentAssertions` reference

* fixed bad `TestKit.ReceiveTests`

* Custom frame size computation support in Framing (#5444)

* Custom frame size computation support in Framing

* Speed up of framing spec

* optimize `Props` `NewExpression` allocations (#5428)

per #5416 (comment)

Co-authored-by: Ismael Hamed <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant