-
Notifications
You must be signed in to change notification settings - Fork 939
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
dri3 extension not supported
error when running with xvfb in GitHub Action
#1277
Comments
Looks like some Chromium issue, would running the tests headless work for you? It even increases the performance since no GUI / xserver needs to be emulated. |
Headless is already working great in the main branch. I'm going headful because the Playwright docs suggest it's necessary to run the browser with an extension. In this case it's an ad blocker. |
Put another way, I'd be happy to adopt any alternative method that works if I can use the ad blocker extension. That's my real goal. I don't really care if the operation is headful or headless. |
I'm continuing to fumble around with this bug, which has become a blocker to my itty bitty humble project. One development: If I add the |
Sorry for the late reply. Were you able to reproduce it with the Chromium which Playwright ships? Since you are using Google Chrome from the operating system. |
Closing as part of triage |
This worked for me: https://shouv.medium.com/how-to-run-cypress-on-wsl2-989b83795fb6 |
Hello. I'm trying to run a headful Playwright browser inside GitHub Actions and running into trouble. I suspect this has to do with some nuance of configuring xvfb or the like.
My current roadblock is that unit tests and manual runs that work properly on my laptop are failing in GitHub Actions with an error that ends
dri3 extension not supported
and reads:More information is available here in the action run: https://github.com/palewire/news-homepages/runs/6248046186?check_suite_focus=true
Any help sorting out the issue would be appreciated.
The text was updated successfully, but these errors were encountered: