Comments on: Howto: Find Regression Windows Through Manual Binary Search

By: The Rumbling Edge :: Talk at Outblaze, Hong Kong

The Rumbling Edge :: Talk at Outblaze, Hong Kong — Fri, 19 Jun 2009 09:07:11 +0000

[...] particular, I was told that my HOWTO find a manual regression window blogpost was particularly useful. (Drop me a quick email if any of my posts are interesting, OK? My email [...]

By: Gary Kwong

Gary Kwong — Wed, 25 Feb 2009 17:04:18 +0000

@Nomis101: Thanks for the headsup!

@Peter: I agree, so I chose to wait 10-15 mins instead to get the builds off FTP.

That said, it could be due to my geographical location, though Mozilla FTPs probably are global. :-/

By: Peter

Peter — Wed, 25 Feb 2009 16:53:49 +0000

I found the slow download speed from the Mozilla FTP to also be quite limiting. I wonder if that can be improved somehow for people doing QA who are not near Mozilla Hq.

@Simon, @Gary: |hg bisect| works nicely. But if you don’t already have a clue where the error is the recompilations will make the whole process even slower than downloading. (And if you rebuild only partly, it may be broken at times.)

By: Nomis101

Nomis101 — Wed, 25 Feb 2009 16:20:28 +0000

It looks like |hg bisect| is the same than |git bisect|
http://www.selenic.com/mercurial/wiki/index.cgi/BisectExtension

By: Gary Kwong

Gary Kwong — Tue, 24 Feb 2009 19:40:01 +0000

@Simon, I know hg has |hg bisect| but I’m not sure whether it’s the equivalent of |git bisect| though.

By: Henrik

Henrik — Tue, 24 Feb 2009 17:24:07 +0000

Please also check out the following discussion in the newsgroups. Would be nice to have such a feature for the QAC extension:

http://groups.google.com/group/mozilla.dev.quality/browse_thread/thread/c6475e51bbb6c618

By: Simon

Simon — Mon, 23 Feb 2009 21:43:09 +0000

Does hg provide some kind of support for an automatic binary search, like ‘git bisect’ does? If so, and if you can test for the bug automatically, then this kind of thing becomes an awful lot easier…

By: Dorus

Dorus — Mon, 23 Feb 2009 20:53:15 +0000

What i do when searching a regression window, is that i also try to speed up exponentially when looking back. Each time doubling the jump i make. In your situation that would probably meand i skipped Shredder Alpha 3 and Shredder Alpha 1, but once i found the bug in 2.0.0.19 i would have checked Shredder Alpha 1 anyway to half the range again