John "codefu" McDole

@yjbanov : I'm going to look into setting the url and ref to force the correct checkout. @sma - the install is just a git check out. If you `git...

Going back and looking at some logs for the first failure: * The other orchestrator builds were happy with the tags and able to get the correct version * It...

The specific luci/recipe section that has me questioning my sanity: `recipe_modules/repo_util/api.py` ```python def engine_checkout( ... git_url = REPOS[engine_repo] git_id = self.m.buildbucket.gitiles_commit.id git_ref = self.m.buildbucket.gitiles_commit.ref if 'git_url' in self.m.properties and 'git_ref'...

That said; I'm running on one cup of coffee and I keep coming back to: the orchestrator just calls git fetch and gets the wrong fetch_head. Could this be because...

The git_ref for api.py checkout: ```python git_ref = ( ref or self.m.buildbucket.gitiles_commit.id or self.m.buildbucket.gitiles_commit.ref or 'refs/heads/%s' % REPO_BRANCHES[name] ) ``` the call to this in engine_v2 (which is not gclient)...

in `.recipe_deps/depot_tools/recipes/recipe_modules/git/api.py`: ```python # There are five kinds of refs we can be handed: # 0) None. In this case, we default to api.buildbucket.gitiles_commit.ref. # 1) A fully qualified branch...

It was pointed out that the only place `gitilesCommit` is not copied over is on a retry - and it looks like the failed build here was a retry. The...

build linux_host_engine 8727887820311286353 failed and was [rescheduled](https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20linux_host_engine/13620/overview) with the correct gitiles. Uploads look correct. Waiting for post submits before closing.

woot

# Monorepo Migration Completed > **TL;DR: Please migrate your PR to flutter/flutter** The `flutter/engine` repository has been migrated to the `flutter/flutter` repository. This PR will no longer be landed here...