Keep runtime alive while async ccall is running

[sbc100]

Without this, when EXIT_RUNTIME is set, the runtime will exit when when we return the event loop.

[kripken]

lgtm % comment

How are tests passing given , is not a valid character in a test name? Is it just skipping invalid names silently..?

[sbc100]

lgtm % comment

How are tests passing given , is not a valid character in a test name? Is it just skipping invalid names silently..?

I guess you can pragmatically create functions with arbitrary names like that. The test certainly runs:

$ ./tests/runner wasm2.test_async_ccall_promise*
Test suites:
['test_core']
Running test_core: (2 tests)
Using 2 parallel test processes
test_async_ccall_promise_exit_runti,e (test_core.wasm2) ... ok (1.65s)
test_async_ccall_promise (test_core.wasm2) ... ok (1.73s)

[sbc100]

lgtm % comment

How are tests passing given , is not a valid character in a test name? Is it just skipping invalid names silently..?

I guess you can pragmatically create functions with arbitrary names like that. The test certainly runs:

$ ./tests/runner wasm2.test_async_ccall_promise*
Test suites:
['test_core']
Running test_core: (2 tests)
Using 2 parallel test processes
test_async_ccall_promise_exit_runti,e (test_core.wasm2) ... ok (1.65s)
test_async_ccall_promise (test_core.wasm2) ... ok (1.73s)

[kripken]

Oh wow, how flexible of python to allow such names... neat.