Block the service worker in contexts a browser test opens itself #1047
No reviewers
Labels
No labels
accessibility
authentication
breaking change
bug
documentation
enhancement
interface
internationalisation
observability
performance
security
tier
1
tier
2
tier
3
tier/4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Postulo/postulo!1047
Loading…
Reference in a new issue
No description provided.
Delete branch "1046-service-worker-contexts"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #1046
The browser job of #1041 hung twice in
tests/e2e/test_column_filters.py: two live-server threads were stuck in SQLite, one serving the job list and one serving/offline/, which only the service worker asks for.browser_context_argsblocks the worker (#895), but only for thepageandcontextfixtures. The 79 contexts the tests open withbrowser.new_context()(phone viewports, scripts off) still installed it. Its background fetch of the offline page overlapped the next request on the live server's single shared in-memory SQLite connection.tests/e2e/conftest.pynow defaultsservice_workersto"block"onBrowser.new_contextfor the session. An explicit value still wins:test_web_app.pypasses"allow"through its ownbrowser_context_args, and its tests pass.Locally:
pytest -m e2e --browser chromium tests/e2e/test_column_filters.py tests/e2e/test_web_app.py: 29 passed.🤖 Generated with Claude Code