Can you explain what you mean by "impossible"? What happens when you run git pull in the bot's checkout? Do you have any logs?

The bot's checkout wouldn't ever update, even though the cache dir was updating to ToT... the bot is now blown away, so I don't know how much testing etc can be performed now :(

This is reproducible on any bot, I believe. Log in, run 'make stop' in slave dir, cd to a chrome dir, try running 'git fetch', and then 'git pull' or 'git checkout origin/master'. It will never check out anything beyond the last commit it had when stopped, despite the .git config having seemingly the right thing set up re: cache.

I have not yet reverse engineered via looking at build stdio logs the precise git fetch/pull/checkout/etc. commands the builder runs when it is not stopped. That is likely the next thing to do.

This is not a Git Admin task. Triaging accordingly.

tl;dr because of local git cache

If you look at git remote origin, you'll see that it's not pointing to https://.../chromium/src, but to some local folder. So, one way around is going to cache folder, running git fetch on it, then running git fetch on specific builder checkout.

Also, gclient sync (and bot_update) understands git cache and does this under the hood.

In the case that resulted in this bug, the git cache folder would not update either.

Run: git_cache.py populate --ignore_locks -v --cache-dir /b/c/git_cache https://chromium.googlesource.com/chromium/src.git

Or just go to /b/c/git_cache, find the chromium/src.git folder, and run a git pull in there, then pull the checkout.

Alternatively, add a new remote to the checkout in question and pull from that new remote.  ie git remote add other https://..../chromium/src, git fetch other

There's no documentation because we actively discourage people from ssh-ing into bots to do things, tho we understand it has to be done from time to time.

Can all this logic be included in gclient somehow if certain error conditions are present (git cache not matching the current date, etc).

Gclient respects git_cache, so actually gclient would work on the solution (except for the root solution, aka chormium/src.git) because it's in unmanaged mode.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot