Skip to content

Firefox E2E tests are failing with "Page closed" #21355

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
silverwind opened this issue Oct 6, 2022 · 4 comments
Closed

Firefox E2E tests are failing with "Page closed" #21355

silverwind opened this issue Oct 6, 2022 · 4 comments

Comments

@silverwind
Copy link
Member

silverwind commented Oct 6, 2022

https://drone.gitea.io/go-gitea/gitea/61116/4/7

Seems like a persistent failure. Maybe @kdumontnu has any ideas. Otherwise, I suggest disabling Firefox.

silverwind added a commit to silverwind/gitea that referenced this issue Oct 6, 2022
Make CI green again, until we figure out
go-gitea#21355.
zeripath pushed a commit that referenced this issue Oct 6, 2022
Make CI green again, until we figure out
#21355.
@wxiaoguang
Copy link
Contributor

wxiaoguang commented Oct 7, 2022

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.


ref, I opened an issue in playwright:

@silverwind
Copy link
Member Author

Where do you see that error? As for playwright issues, I found microsoft/playwright#17688, but it's not really helpful.

@wxiaoguang
Copy link
Contributor

Where do you see that error? As for playwright issues, I found microsoft/playwright#17688, but it's not really helpful.

I collected the logs for microsoft/playwright#17876 from our CI/CD pipeline by #20744

@kdumontnu kdumontnu mentioned this issue Jun 5, 2023
2 tasks
@wxiaoguang
Copy link
Contributor

Firefox test has been disabled for long time, maybe it doesn't fail now but there seems no need for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants