Before running the actual culprit-finding logic in the Findit recipes, it is helpful to record the chromium revision of code checkout so that we know how old the code checkout is. This will make our monitoring for speed more comparable.
Sometimes I may rerun an old analysis to confirm my change works, which means I may checkout a much older revision, and that will affect this data. Should we do something about this case?
That's why I tried to look at 'origin/master' instead of whatever is currently checked out. Am I wrong to assume that origin/master will be at the latest available revision?
My undestanding was that when you checkout an older revision, the revision is checked out with a floating head, but the remote branches aren't changed.
maybe @iannucci can shed light here, he's more familiar with this (please refer to the CL for more details: https://chromium-review.googlesource.com/c/475135/ )
Comment 1 by robert...@chromium.org
, Apr 11 2017Status: Assigned (was: Available)