lv_micropython/tests/ports/webassembly/asyncio_top_level_await.mjs.exp

= TEST 1 ==========
top-level wait event
callback set event
top-level end
finished
= TEST 2 ==========
top-level wait task
task start
callback cancel task
top-level task CancelledError True
finished
= TEST 3 ==========
top-level wait event
task set event
task sleep
top-level wait task
task end
top-level end
finished
webassembly/asyncio: Schedule run loop when tasks are pushed to queue. In the webassembly port there is no asyncio run loop running at the top level. Instead the Python asyncio run loop is scheduled through setTimeout and run by the outer JavaScript event loop. Because tasks can become runable from an external (to Python) event (eg a JavaScript callback), the run loop must be scheduled whenever a task is pushed to the asyncio task queue, otherwise tasks may be waiting forever on the queue. Signed-off-by: Damien George <damien@micropython.org> 2024-06-19 15:04:12 +10:00			`= TEST 1 ==========`
			`top-level wait event`
			`callback set event`
			`top-level end`
			`finished`
			`= TEST 2 ==========`
			`top-level wait task`
			`task start`
			`callback cancel task`
			`top-level task CancelledError True`
			`finished`
			`= TEST 3 ==========`
webassembly/asyncio: Support top-level await of asyncio Task and Event. This change allows doing a top-level await on an asyncio primitive like Task and Event. This feature enables a better interaction and synchronisation between JavaScript and Python, because `api.runPythonAsync` can now be used (called from JavaScript) to await on the completion of asyncio primitives. Signed-off-by: Damien George <damien@micropython.org> 2024-06-18 17:35:24 +10:00			`top-level wait event`
			`task set event`
			`task sleep`
			`top-level wait task`
			`task end`
			`top-level end`
			`finished`