Lines Matching refs:good
10 known-good revision. It will then binary search across this revision range by
814 last known good revision."""
1370 """Given known good and bad values, decide if the current_value passed
1430 # this directory directly won't give much good info.
1477 known good and bad revisions.
1480 good_rev: The last known good revision where the performance regression
1552 good_revision: Last known good revision.
1555 A tuple with the new bad and good revisions.
1597 good_revision: Number/tag of the known good revision.
1601 True if the revisions are in the proper order (good earlier than bad).
1618 """Given known good and bad revisions, run a binary search on all
1624 good_revision: Number/tag of the known good revision.
1689 # Check that they didn't accidentally swap good and bad revisions.
1743 # Perform the performance tests on the good and bad revisions, to get
1768 # Can just mark the good and bad revisions explicitly here since we
1965 print ' -> Last Good Revision: [%40s] [%s]' %\
2053 'deviations from "good" value. Results may not be accurate.')
2075 # If the "good" valuse are supposed to be higher than the "bad"
2266 'Must be later than good revision. May be either a git' +
