On Fri, Mar 16, 2012 at 1:04 PM, Brandon Allbery <allber...@gmail.com> wrote: > On Fri, Mar 16, 2012 at 12:56, Nicholas Clark <n...@ccl4.org> wrote: > >> On Fri, Mar 16, 2012 at 07:51:44AM -0700, Moritz Lenz wrote: >> > Somwhere between the 2012.02 release and 2012.02-180-g16bf0f4, test 253 >> > in S05-mass/rx.t started to fail: >> >> Isn't this were a git bisect is a routine way to find out the cause? >> > > Only when you don't need to tie the repo you're bisecting to > commit-specific versions of some independent repo (viz. Parrot). (darcs > trackdown doesn't know how to do that either....) > > -- > brandon s allbery allber...@gmail.com > wandering unix systems administrator (available) (412) 475-9364 vm/sms
In this case, if you build rakudo with --gen-parrot, you'll whatever the recommended version for that release of rakudo. So, you could remove the ./install directory before each bisect run and get a version of parrot that will at least probably work with that version of rakudo. -- Will "Coke" Coleda
