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
[taskcluster] Disable Chrome sandboxing in Docker #20152
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
infrastructure/ tests
now pass, which suggests our change in run.py
is working as intended.
However, I don't know why tools/wpt/ tests
still fail. See my inline comments.
Whenever we see TASKCLUSTER_ROOT_URL in the entry point (runl.py), we disable Chrome sandboxing with --no-sandbox. Fix #20133
954ffb5
to
a175c9c
Compare
Turns out I was looking at the wrong |
Even though we don't really rely on this env var in this suite for now, it makes sense to have it everywhere for consistency.
cc @stephenmcgruer this should hopefully pass everything and I've also dropped the debug commits. I need to shoot off now. In case this still fails, could you take a look and talk to James? It'd really be great to have this merged before tomorrow so that we can finish our migration before the deadline. |
Ack, will monitor how it goes. |
Whenever we see
TASKCLUSTER_ROOT_URL
in the entry point (runl.py
), wedisable Chrome sandboxing with --no-sandbox.
tox.ini needs to be modified to allow passing of
TASKCLUSTER_ROOT_URL
.Fix #20133
(Alternative to #20136 )