Investigate Linux docs_publish and docs_test failures

[Renzo-Olivares]

The tree is currently red on Linux docs_test and Linux docs_publish.

Failed: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20docs_test/7600/overview
Re-run: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20docs_test/7601/overview
Re-run:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20docs_test/7602/overview

I'm seeing

Infra Failure: Step('Install dashing') (retcode: 1)

and

package github.com/urfave/cli/v2: cannot find package "github.com/urfave/cli/v2" in any of:
    /b/s/w/ir/cache/go/src/github.com/urfave/cli/v2 (from $GOROOT)
    /b/s/w/ir/x/w/recipe_cleanup/go_path/src/github.com/urfave/cli/v2 (from $GOPATH)

For Linux docs_publish

Failed: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20docs_publish/7495/overview
Re-run: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20docs_publish/7496/overview
Re-run: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20docs_publish/7497/overview
Re-run: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20docs_publish/7498/overview

[keyonghan]

This sounds we need to use a newer version of go. The one we are using is 2 years ago: https://chrome-infra-packages.appspot.com/p/infra/go/linux-amd64/+/.

By using the fuchsia go version: https://chrome-infra-packages.appspot.com/p/fuchsia/go/linux-arm64/+/, an LED run passes the dashing install step: https://luci-milo.appspot.com/raw/build/logs.chromium.org/flutter/led/keyonghan_google.com/cc428ec3c1e497f253620e08f81317d24e200406d30f8311aa0359659f0337e4/+/build.proto

[keyonghan]

Switched to maintainable 3pp one:
https://flutter-review.git.corp.google.com/c/recipes/+/35820

LED run: https://luci-milo.appspot.com/raw/build/logs.chromium.org/flutter/led/keyonghan_google.com/2c27e9df205b6ef60b16f0c12bc38034ffe71f818efa0794680d758c371d5861/+/build.proto

[Renzo-Olivares]

The fix above has been merged. Tree is now green.

[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.