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
Mac_arm64 tool_host_cross_arch_tests
is failing with recipe crash
#113231
Comments
cc oncall @drewroengoogle |
It seems like the |
Unassigning after discussion with @godofredoc about whether this is an infra issue. |
@drewroengoogle do you know who is working on this? Is |
@jmagman Thanks for following up, I meant to yesterday but got sidetracked. |
I took a quick look, removing the installation of ruby makes the gems steps to succeed but all the tests fail. E.g. for x64 GEM_HOME is set to a generic folder where blundler and bundle are installed https://cs.opensource.google/flutter/recipes/+/main:recipe_modules/flutter_deps/api.py;l=300 and only after the gems path has been set and gems have been installed the path is changes to the ruby specific location https://cs.opensource.google/flutter/recipes/+/main:recipe_modules/flutter_deps/api.py;l=326 In arm64 GEM_HOME is set directly to <gem_dir>/ruby/3.1.0 when the bundler and bundle are located at <gem_dir> Another potential problem is that ruby binaries from cipd are installed at the end of the path and most likely never used is ruby is already installed in the system or the code is running from an xcode context. https://cs.opensource.google/flutter/recipes/+/main:recipe_modules/flutter_deps/api.py;l=282 |
Compared the failed build with succeeded one, the env. |
Chromium team reinstalled our bots on 10/07 morning, which is aligned with our incident here. It is suspected some hard coded paths somewhere. |
Apart from the what actually caused this problem. We need to make this installation hermetic and resilience to changes in the environment. |
Yeah, I agree. When creating the ruby version, a prefix path is needed to make it work. I believe that's the culprit here. |
Have spent quite some hours to work on the portable version, but still no luck to make it work. I am running out of ideas.. Anyone with experience on ruby may have a better idea on how to make it work? /cc @jmagman One possible workaround is build/deploy openssl and ruby on the runtime, but it will add 5+ mins on each run. |
Were you able to figure out why |
Devicelab vs chromium machines? |
Yeah, these are devicelab testbeds where the root dirs are not changed (still /opt/s), whereas the chromium ones have been updated to |
@yusuf-goog FYI |
This is fixed now with ruby hermetic packages and https://flutter-review.googlesource.com/c/recipes/+/38088 |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8800893589239561057/+/u/RECIPE_CRASH__Uncaught_exception_/logging
This test is marked
bringup:true
due to #112130, but was previously successfully passing in staging.The text was updated successfully, but these errors were encountered: