git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v3 0/3] automatically skip away from broken commits

From
HAH. Peter Anvin <hpa@zytor.com>
Date
Jun 8, 2009, 15:51 UTC
Message-ID
<4A2D337C.70203@zytor.com>
In-Reply-To
<7vws7n6vcf.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
Show 22 quoted lines
> "H. Peter Anvin" <hpa@zytor.com> writes:
> 
>> It's not entirely clear to me that this is any better than simply
>> randomly picking a commit from the list of plausible commits -- in other
>> words, eliminate the commits we can totally rule out, and then just pick
>> a random commit among the list of plausible commits.  This is not
>> *quite* as crazy as it sounds; it has the advantage of being an
>> extremely simple algorithm which shouldn't have any pathological behaviours.
> 
> That is essentially what Christian's patch does.  It does not try to go
> away from untestable commits in topological space.  Instead, when we find
> that the commit with the best "goodness" value is known to be untestable,
> we step away from that commit by some alternating distance _in the
> goodness value space_ (which does not have much to do with how commit
> ancestry topology is laid out).  Viewed in the topology space, it is quite
> similar to picking a different commit randomly, except for a very special
> case where the remaining history is completely linear, in which case the
> goodness value space and ancestry topology have a direct correlation.
> 
> That special case, and the deterministic hence repeatable nature of the
> algorithm, are the two main advantages over picking a completely random
> commit among the list of plausible commits.

Well, the cyclic "stepping distance" is pretty much a really lame PRNG in this case. In the linear case I think the distances are rather arbitrary (and suboptimal), and I'm not sure it wouldn't simply be better to actually use a PRNG (which can be unseeded and therefore repeateable, or perhaps even better seeded with some combination of the hash values involved.)

The advantage of that -- and I have to admit I don't know if it will ever matter in practice -- is that using an actual PRNG:

a) is less likely to get into pathological capture behaviors.
b) doesn't make people think later that there is something magic to the
   arbitrary chosen numbers.
	-hpa
-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.
Previous: Junio C HamanoNext: Junio C Hamano
Message 9 of 37 in “automatically skip away from broken commits”
  1. 0/3 automatically skip away from broken commitsChristian Couder, Jun 6, 2009
  2. 1/3 bisect: add parameters to "filter_skipped"Christian Couder, Jun 6, 2009
  3. 2/3 bisect: when skipping, choose a commit away from a skipped commitChristian Couder, Jun 6, 2009
  4. 3/3 t6030: test skipping away from an already skipped commitChristian Couder, Jun 6, 2009
  5. Junio C HamanoJun 6, 2009
  6. Christian CouderJun 7, 2009
  7. H. Peter AnvinJun 8, 2009
  8. Junio C HamanoJun 8, 2009
  9. H. Peter AnvinJun 8, 2009
  10. Junio C HamanoJun 8, 2009
  11. H. Peter AnvinJun 8, 2009
  12. Christian CouderJun 9, 2009
  13. Jakub NarebskiJun 9, 2009
  14. H. Peter AnvinJun 9, 2009
  15. Jakub NarebskiJun 9, 2009
  16. H. Peter AnvinJun 9, 2009
  17. Christian CouderJun 9, 2009
  18. H. Peter AnvinJun 9, 2009
  19. Junio C HamanoJun 9, 2009
  20. H. Peter AnvinJun 9, 2009
  21. Christian CouderJun 9, 2009
  22. H. Peter AnvinJun 9, 2009
  23. Christian CouderJun 10, 2009
  24. Junio C HamanoJun 9, 2009
  25. Christian CouderJun 10, 2009
  26. Junio C HamanoJun 10, 2009
  27. H. Peter AnvinJun 10, 2009
  28. Christian CouderJun 11, 2009
  29. H. Peter AnvinJun 11, 2009
  30. H. Peter AnvinJun 11, 2009
  31. Christian CouderJun 12, 2009
  32. H. Peter AnvinJun 13, 2009
  33. Jakub NarebskiJun 13, 2009
  34. H. Peter AnvinJun 13, 2009
  35. Christian CouderJun 15, 2009
  36. H. Peter AnvinJun 15, 2009
  37. Christian CouderJun 13, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.