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
Going on the above (see section "Why does this only affect developer builds?"), using stable as release version rather than latest (which is the default) in the setup-chrome workflow config should fix the problem: https://github.com/browser-actions/setup-chrome
Sometimes our accessibility workflow task fails with error "no usable sandbox":
https://github.com/ScottLogic/blog/pull/287/checks#annotation:13:9
This seems to be due to Ubuntu linux restricting unprivileged namespace access:
https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md
Going on the above (see section "Why does this only affect developer builds?"), using
stable
as release version rather thanlatest
(which is the default) in the setup-chrome workflow config should fix the problem:https://github.com/browser-actions/setup-chrome
While we are fixing that, we should also make use of the output from this action when invoking chrome in the subsequent "Run pa11y-ci" step. See https://github.com/browser-actions/setup-chrome?tab=readme-ov-file#installed-path
The text was updated successfully, but these errors were encountered: