-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[SpecFix] working on fixing AtLeastOnceDeliveryCrashSpec #3806
[SpecFix] working on fixing AtLeastOnceDeliveryCrashSpec #3806
Conversation
…igured_with_a_failing_directory
Task.Run(() => | ||
{ | ||
Thread.Sleep(10); | ||
return msg; | ||
}).PipeTo(Sender, Self); //LogicalContext is lost?!? | ||
}).PipeTo(sender, self); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed this spec too - would sometimes fail because we didn't close over Sender
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This isn't the final fix here - still having issues.
Still having issues with |
…3806) * akkadotnet#3786 - working on fixing AtLeastOnceDeliveryCrashSpec * fixed issue with SnapshotDirectoryFailureSpec.LocalSnapshotStore_configured_with_a_failing_directory * fixed Akka.Persistence.Tests.Actor_PipeTo_should_not_be_delayed_by_async_receive * looks like issue might be related to parallel execution and thread blocking * added logging for AtLeastOnceDelivery_must_tolerate_and_recover_from_random_failures
…3806) * akkadotnet#3786 - working on fixing AtLeastOnceDeliveryCrashSpec * fixed issue with SnapshotDirectoryFailureSpec.LocalSnapshotStore_configured_with_a_failing_directory * fixed Akka.Persistence.Tests.Actor_PipeTo_should_not_be_delayed_by_async_receive * looks like issue might be related to parallel execution and thread blocking * added logging for AtLeastOnceDelivery_must_tolerate_and_recover_from_random_failures
#3786 - added some debug logging to see why this test is racy. Looks like it's either an issue with Recovery, the timing configuration of the
AtLeastOnceDeliveryActor
in this spec, or theAtLeastOnceDeliverySemantic
not handling recoveries properly.