Calculate the path to gems file directly from the generated folder

[godofredoc]

The gems bundler is adding a the ruby version in the path and it may be different depending on the test bed it is running. We need to get the values to add to the path and GEM_HOME env directly from the generated folder instead of hardcoding the path to a given version of ruby.

[godofredoc]

\cc @christopherfujino

[godofredoc]

\cc @jmagman @drewroengoogle @ricardoamador this is related to the error in arm64 cross arch tests.

[christopherfujino]

The way rubygems is designed does not play nicely with a tool like cipd. @ricardoamador do you have a build log with a relevant crash?

[ricardoamador]

@christopherfujino take a look here: https://ci.chromium.org/p/flutter/builders/staging/Mac_arm64%20tool_host_cross_arch_tests?cursor=id%3E8800936530191176481&limit=25
The error reported each time is this:

Uncaught Exception: FileNotFoundError('2', 'No such file or directory')

[christopherfujino]

Per the stacktrace, it looks like this line is failing:

        api.flutter_deps.gems(
            env, env_prefixes, checkout_path.join('dev', 'ci', 'mac')
        )

And not the flutter_deps module itself, which surprises me.

[christopherfujino]

Per the stacktrace, it looks like this line is failing:

        api.flutter_deps.gems(
            env, env_prefixes, checkout_path.join('dev', 'ci', 'mac')
        )

And not the flutter_deps module itself, which surprises me.

However, per the steps that we see rendered, we must have hit api.flutter_deps.gems(). Another case where I'm stumped because I don't know how python works...

Ahh ok never mind, I was reading the stacktrace upside down, we are indeed inside flutter_deps.gems

[christopherfujino]

So it looks like we're installing bundler into gem_dir: https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8800936626246555681/+/u/Install_gems/install_bundler/execution_details

Maybe the solution here is to invoke bundler with the absolute path here: https://flutter.googlesource.com/recipes/+/refs/heads/main/recipe_modules/flutter_deps/api.py#319

[ricardoamador]

Correct. I think that is what Godofredo is saying here.

[godofredoc]

Removing myself from this bug, @drewroengoogle @keyonghan this can addressed when landing the changes to the ruby cipd package.

[godofredoc]

Fixed with https://flutter-review.googlesource.com/c/recipes/+/38088

[github-actions]

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 flutter doctor -v and a minimal reproduction of the issue.