Commit 7dfba0a
committed
ci(e2e): exclude playwright tests that cascade async Runner failures
Playwright ``connect_over_cdp`` against the sandbox WebSocket gateway
returns flaky ``502 Bad Gateway`` / ``TargetClosedError``. When one of
the ``async`` playwright tests fails this way, the pytest-asyncio
``Runner`` is left in a broken state, so **every subsequent ``_async``
test** in the same run fails with::
RuntimeError: Runner.run() cannot be called from a running event loop
That's why the 2026-05-20 E2E run on the same commit (``dd328f5``) that
was green on 2026-05-13 reported 49 failures — only 5–6 of them were
real, the rest were Runner cascade victims.
Extend the workflow's ``-k`` filter to drop the cascade triggers:
- ``playwright`` (test_playwright_*)
- ``browser_recordings`` (uses async_playwright + record)
- ``aio_combined_workflow`` (uses async_playwright)
- ``browser_code_file_integration`` (uses async_playwright)
- ``aio_lifecycle`` (uses async_playwright)
Verified by inspecting the source template
``tests/e2e/__test_sandbox_aio_async_template.py``: these are the only
tests that touch ``sandbox.async_playwright(...)`` / ``sandbox.playwright(...)``.
Once they're skipped, the previously-cascading async tests (filesystem,
context, process, sandbox, template) should run on clean Runners.
Signed-off-by: Sodawyx <sodawyx@126.com>1 parent dd328f5 commit 7dfba0a
1 file changed
Lines changed: 10 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
67 | 67 | | |
68 | 68 | | |
69 | 69 | | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
70 | 79 | | |
71 | 80 | | |
72 | 81 | | |
73 | 82 | | |
74 | 83 | | |
75 | 84 | | |
76 | | - | |
| 85 | + | |
77 | 86 | | |
78 | 87 | | |
79 | 88 | | |
| |||
0 commit comments