search

actions / runner-images

GitHub Actions runner images
MIT License
10.15k stars 3.06k forks source link

Google Chrome tests failing on Ubuntu 22.04 #7115

Closed markatky46 closed 1 year ago

markatky46 commented 1 year ago

Description

Error has started since our last build 3 weeks ago. The test to describe Chrome fails with the following error. This is executed during the step: linux/scripts/installers/google-chrome.sh

azure-arm.build_vhd: Running tests from '/imagegeneration/tests/Browsers.Tests.ps1' azure-arm.build_vhd: Describing Chromium azure-arm.build_vhd: [-] Chromium 113ms (82ms|31ms) azure-arm.build_vhd: Command 'chromium-browser --version' has finished with exit code azure-arm.build_vhd: chromium-browser: error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory azure-arm.build_vhd: at "chromium-browser --version" | Should -ReturnZeroExitCode, /imagegeneration/tests/Browsers.Tests.ps1:39 azure-arm.build_vhd: at , /imagegeneration/tests/Browsers.Tests.ps1:39 azure-arm.build_vhd: Tests completed in 559ms azure-arm.build_vhd: Tests Passed: 0, Failed: 1, Skipped: 0 NotRun: 7

Attempted 4 builds today all failing with same error. Latest main branch pulled each build.

Platforms affected

Runner images affected

Image version and build link

Image Version: 20230206.1

No public link to build.

Is it regression?

no

Expected behavior

Describing Chromium passes successfully and build moves onto scripts/installers/google-cloud-sdk.sh

Actual behavior

Build fails at Describing Chromium with: Command 'chromium-browser --version' has finished with exit code chromium-browser: error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory

Repro steps

Run a build and call linux/scripts/installers/google-chrome.sh via azure-arm build.

erik-bershel commented 1 year ago

Hey @markatky46! Already in progress here: https://github.com/actions/runner-images/pull/7113

markatky46 commented 1 year ago

Thanks for the swift response @erik-bershel, sorry i missed the other fix.

mikhailkoliada commented 1 year ago

Should be fixed.