You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The browser object in code is not related to this problem. The problem here is firefox can not call newPage (even without the browser, the test framework still need to call newPage to open a new page for test).
Just a guess: I can see a suspicious error log Sandbox: thread-synchronized seccomp failed: Unknown error 524, so I suspect that this problem is caused by host docker's seccomp policy. Firefox needs to set seccomp+tsync, but it fails, then firefox crashes.
Activity
Disable Firefox E2E tests
Disable Firefox E2E tests (#21363)
wxiaoguang commentedon Oct 7, 2022
The
browser
object in code is not related to this problem. The problem here is firefox can not callnewPage
(even without the browser, the test framework still need to call newPage to open a new page for test).Just a guess: I can see a suspicious error log
Sandbox: thread-synchronized seccomp failed: Unknown error 524
, so I suspect that this problem is caused by host docker's seccomp policy. Firefox needs to set seccomp+tsync, but it fails, then firefox crashes.ref, I opened an issue in playwright:
silverwind commentedon Oct 7, 2022
Where do you see that error? As for playwright issues, I found microsoft/playwright#17688, but it's not really helpful.
wxiaoguang commentedon Oct 7, 2022
I collected the logs for microsoft/playwright#17876 from our CI/CD pipeline by #20744
wxiaoguang commentedon Apr 23, 2025
Firefox test has been disabled for long time, maybe it doesn't fail now but there seems no need for it.