Yunchi Luo

Hmm that's strange, I would not have expected this to be an architecture-specific problem. My environment is an Apple Silicon Macbook running ``` ❯ java -version openjdk version "17.0.10" 2024-01-16...

Here's the "kotest-PID.log" files. I'm not totally sure how to interpret these logs but I do see the same tests being assigned to multiple PIDs. [kotest-logs.zip](https://github.com/kotest/kotest/files/15295497/kotest-logs.zip)

Thanks for the thorough investigation, the bug makes much more sense now! > So if we changed Kotest to assume an intentional no-op invocation with JUnitPlatform, this would not solve...

Yes, those considerations make sense to me. I agree that adding a property instead of enabling it as a default would be a safer option. As well as getting consensus...

Yes, that seems to have solved the problem of tests running twice! [kotest-logs.zip](https://github.com/kotest/kotest/files/15298964/kotest-logs.zip)

I'm trying to set up an ECS deployment pipeline and running into similar issues. IIUC the workarounds so far, and from #632, with the exception of @WhyNotHugo's template idea, all...

Oh hey @bryantbiggs, I was actually just opening an issue in https://github.com/terraform-aws-modules/terraform-aws-ecs to ask you about this. I've read your design doc multiple times now 😅 I don't quite understand...

I understand that the root of the issue is that `runTest` doesn't offer a method of using virtual time without delay skipping. But I think we can improve the Turbine's...

@jingibus making that change causes 4 tests to fail, 3 of which because the flow under test has delays that use real time with Dispatchers.Default. I only tested on jvm...

Made a PR and fixed those tests. Looks like all tests passed. https://github.com/mightyguava/turbine/actions/runs/6291465123/job/17079856671. Failed on lint Also added a test for delay testing