Aaron Stannard

## `dev` ``` BenchmarkDotNet v0.14.0, Windows 11 (10.0.22631.4037/23H2/2023Update/SunValley3) 12th Gen Intel Core i7-1260P, 1 CPU, 16 logical and 12 physical cores .NET SDK 8.0.302 [Host] : .NET 8.0.6 (8.0.624.26715), X64...

I'm attempting to reproduce this today and it looks like I no longer can - everything seems to be working ok even with "run until failure" using v1.5.30.1

This makes me wonder if this was an xUnit issue possibly

Yes, it looks like this was an issue that was fixed in xUnit 2.8.0, which we upgraded to in June as part of https://github.com/akkadotnet/Akka.Hosting/pull/463 xUnit release notes here: https://xunit.net/releases/v2/2.8.0

Welp, I take that back - was able to reproduce the failure with ```csharp [Fact] public async Task ShouldAllowDuplicatePauseCommands() { // arrange var cohortId = TestCohortId; var cohortActor = await...

This might be resolved via https://github.com/akkadotnet/akka.net/pull/7674

Gonna mark this down as a "developer experience" issue because that's kind of how I feel about it - one knock-on effect this might have though, if we implement it,...

Thanks for the PR - looks like this broke some tests

> It seems that the framework relies on this behavior. For example, test `Inbox_Receive_will_timeout_gracefully_if_timeout_is_already_expired` uses `Akka.Actor.Inbox.Receive` that calls `Ask` and expects the result to be `Status.Failure`. A bit of a...

Thanks for weighing in @lucavice - I agree with all of this. Changing the behavior was probably the right call so the PR was a good idea, but yeah it's...