Skip to content
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

fix browser-test job #2639

Merged
merged 1 commit into from
Feb 18, 2025
Merged

fix browser-test job #2639

merged 1 commit into from
Feb 18, 2025

Conversation

mroderick
Copy link
Member

@mroderick mroderick commented Feb 18, 2025

Purpose (TL;DR) - mandatory

When running browser-test job on ubunty-latest the following error is emitted:

Error: Failed to launch the browser process!
[1999:1999:0210/184211.279511:FATAL:zygote_host_impl_linux.cc(128)] No usable sandbox! If you are running on Ubuntu 23.10+ or another Linux distro that has disabled unprivileged user namespaces with AppArmor, see https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md. Otherwise see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the (older) SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
[0210/184211.290099:ERROR:file_io_posix.cc(145)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[0210/184211.290150:ERROR:file_io_posix.cc(145)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)

The root cause of the error is described at https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md

By locking browser-test to ubuntu-22.04, we can avoid this error, while a more
elegant solution is found.

How to verify

Observe that all the GitHub Actions are green for this branch 🟢

When running `browser-test` job on `ubunty-latest` the following error is emitted:

```
Error: Failed to launch the browser process!
[1999:1999:0210/184211.279511:FATAL:zygote_host_impl_linux.cc(128)] No usable sandbox! If you are running on Ubuntu 23.10+ or another Linux distro that has disabled unprivileged user namespaces with AppArmor, see https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md. Otherwise see https://chromium.googlesource.com/chromium/src/+/main/docs/linux/suid_sandbox_development.md for more information on developing with the (older) SUID sandbox. If you want to live dangerously and need an immediate workaround, you can try using --no-sandbox.
[0210/184211.290099:ERROR:file_io_posix.cc(145)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[0210/184211.290150:ERROR:file_io_posix.cc(145)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
```

The root cause of the error is described at https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md

By locking `browser-test` to `ubuntu-22.04`, we can avoid this error, while a more
elegant solution is found.
@mroderick mroderick requested a review from hexeberlin February 18, 2025 13:48
@mroderick mroderick marked this pull request as ready for review February 18, 2025 13:48
@mroderick mroderick changed the title WIP: try to fix browser-test job fix browser-test job Feb 18, 2025
@mroderick mroderick merged commit 0ca2e49 into main Feb 18, 2025
13 checks passed
@mroderick mroderick deleted the fix-browser-test branch February 18, 2025 13:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants