Can you provide a full code or anything runnable? There might be already a hidden magic global for you to try it out:

const ctrl = new AbortController();
__vitest_worker__.onCancel.then(() => ctrl.abort())

The code I'd need to use this is a bit complex; but in essence, the example in the suggested solution maps well to what I have - a test that spawns a k6 process to loadtest (of varying durations, but often long running) a server. Sometimes, setting up the test, requires running Docker containers that are cleaned up in afterAll hooks and if you terminate the run (double CTRL+C), the containers are left running after the run ends.

Now, if there's an option where I can listen on run cancellation requests, I could gracefully kill the k6 process, releasing the "wait" of the loadtest early allowing for the afterAll hooks to run.

BTW, thanks for the hint! I'll try that one out. 👍

I like the idea of providing a signal, but I am not sure if it will help with your use case. Double CTRL+C always kills the process and everything that was hanging will continue hanging even if we provide a signal (which internally will work just like @hi-ogawa proposed).

In any case, I think we should expose a signal to tests.

The idea is to not use the double CTRL+C, but use q or a single CTRL+C to gracefully stop long-running tests.

@enisdenjo Can you confirm whether #7647 (comment) works for you just in case? It would be unfortunate if there's some others factor to it and something not working after implemented builtin. Also, it's still nice to have a simplified repro so we can add it as test for what users do.

Sorry, I forgot to leave a reply - yes #7647 (comment) does what I want!

Regarding the repro, I can add the test itself - just point me to the test file. 😄

As a note, it would also be nice to abort the signal if test times out. This is how it works in node test runner, for example:

import { test } from 'node:test'
import { setTimeout } from 'timers/promises'

test('example', { timeout: 100 }, async t => {
  t.signal.addEventListener('abort', (e) => {
    console.log('aborted', e) // Event
  })
  await setTimeout(1000)
})

@sheremet-va +1, I also need an abort signal in each test, like node:test.

	tc.test('reuse token', async (tc) => {
		let provider = new StaticCredentialsProvider({ username, password }, cs.origin, cf)

		let token = await provider.getToken(false, tc.signal)
		let token2 = await provider.getToken(false, tc.signal)

		assert.strictEqual(token, token2, 'Token is the same')
		assert.strictEqual(calls, 1, 'Only one call was made')
	})

The main task is to be able to interrupt promises, async and background processes.
In my example, getToken can do a lot more background work after the promise is resolved, and when using signal, it can be interrupted.