I have a spec class that is hanging after the last test completes. All tests run and pass, but test execution does not finish. I have a logging listener registered. The

afterAny

gets called for the last test and the test container, the

afterContainer

gets called, but the

afterSpec

function does not get called. Does anyone know what happens between

afterContainer

and

afterSpec

that could cause the test execution to hang? Thanks.

after project, perhaps?

I'm pretty sure

afterProject

happens after

afterSpec

, I've added an

afterProject

log to my test and it does not get called.

Do you have anything thready or coroutiny going on in the callbacks ?

In

beforeSpec

, I launch a coroutine in

GlobalScope

which continues in the background (the tests interact with services running there). That launched job is cancelled in an

afterSpec

. The test hangs before that

afterSpec

is called.

anything launched in global scope shouldn't matter

That's what I was thinking.

if you remove that call does the test complete

test cases fail, but the test completes.

doesn't hang anymore? So does sound like something in that coroutine is locking it up

Yeah, that seems odd though right? It's launched in global scope, so how can it interfere with the completion of the test? I can imagine a case where it might prevent the JVM from shutting down, but how would it prevent the call to

afterSpec

?

yeah it doesn't make much sense to me either

That's a good question... this is an integration test, so it starts a handful of other services that the service under test interacts with.

It might be doing something that causes things to hang

I've made the test complete by removing the

coroutineContext

passed to the

launch

function. I had been passing a modified version of the

currentCoroutineContext()

, but with no context argument, the test completes.

not off top of my head but we did do a bunch of work on coroutines in general. I know @Oliver.O knows this stuff pretty well he might be able to help (night time for him right now)

🤷 It's working now

that would be helpful

Thanks for your help.

np

Stuff hanging before afterSpec is called seems exotic. The common case for a hang on exit is a non-daemon thread.

So it turns out it's actually really easy to reproduce. Here is a self-contained test class that hangs:

class KotestHangBeforeAfterSpec : FunSpec(
  {
    lateinit var job: Job
    beforeSpec {
      job = GlobalScope.launch(currentCoroutineContext()) { delay(Duration.INFINITE) }
    }

    afterSpec {
      job.cancel()
    }

    test("always pass") {
      assert(true)
    }
  }
)

thanks for the reproducer and the deep dive

Would you like me to make an issue on GitHub?

yes please

I'll do that in the next few hours. Right now I need to make dinner.

Cool, thanks! I’ll be looking into it.