-
Notifications
You must be signed in to change notification settings - Fork 63
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
Failing to run on ubuntu-22.04 #198
Comments
I had a similar experience with Fedora Core - tests started failing with "Failed to run". In my case, the problem was the browser path, which I fixed by setting |
I've got it working on ubuntu-22.04 by setting the field {
"defaults": {
"chromeLaunchConfig": {
"executablePath": "/usr/bin/google-chrome"
}
}
} |
For CircleCI, I've fixed this by adding {
"defaults": {
"chromeLaunchConfig": {
"args": [
"--no-sandbox"
]
}
}
} See https://github.com/pa11y/pa11y-ci/blob/master/README.md#docker. |
We could add this to the docs. It would be helpful for those configuring CircleCI and Github. If possible I'll submit a PR later. |
Fixes issue on newer Ubuntu versions. See <pa11y/pa11y-ci#198> for details.
A few weeks ago our pa11y-ci tests started failing on Github runners when targeting
ubuntu-latest
, coinciding with Github updatinglatest
to target version 22.04.1 (previously version 20.04.5).We are using the latest version of
![Screenshot 2022-12-20 at 09 46 41](https://user-images.githubusercontent.com/6436551/208640975-67a891bf-b090-4f24-b29e-51cae8a56d72.png)
pa11y-ci
(version 3.0.1).The failure message was
Failed to run
against the URL (as pictured) and the error thrown, logged by the reporter was{"name":"TimeoutError"}
.We updated the Github action to target Ubuntu version 20.04.5 and the tests started passing again. I've looked through the release notes for version 22.04 and can't see anything in particular that might cause these failures.
The text was updated successfully, but these errors were encountered: