bisectable6

query

old=2015.01 42 .say

result

Bisecting: 7604 revisions left to test after this (roughly 13 steps)
[29f487e982a3e6dd8fb330b51e94c7207d13810e] Fix build errors when older version of rakudo-j is installed
»»»»» Testing 29f487e982a3e6dd8fb330b51e94c7207d13810e
»»»»» Script output:
42

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing e66c52e8807ebf727ccffd4710021271f291c943
»»»»» Script output:
42

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing dac0167a17b468760a7d4155b88f40a6509b6429
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/bcBztReMBo
Two terms in a row
at /tmp/bcBztReMBo:1
------> 42⏏ .say
    expecting any of:
        infix
        infix stopper
        statement end
        statement modifier
        statement modifier loop

»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 934893b26e720f7c85d91ab620cf295c8ba7ec71
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/bcBztReMBo
Two terms in a row
at /tmp/bcBztReMBo:1
------> 42⏏ .say
    expecting any of:
        infix
        infix stopper
        statement end
        statement modifier
        statement modifier loop

»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing f3b535578df70a3286640c542cc13785cdebd459
»»»»» Script output:
42

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing bff29c46317efa9e98f1353e7c6cb0497aad1253
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/bcBztReMBo
Two terms in a row
at /tmp/bcBztReMBo:1
------> 42⏏ .say
    expecting any of:
        infix
        infix stopper
        statement end
        statement modifier
        statement modifier loop

»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 1ee7a96c10797643a0f46aa38c8880dafe673340
»»»»» Script output:
42

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 68eed5936cf54dfd991bf661950c68195fb94f5a
»»»»» Script output:
42

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 3813a26d1e94ed07e441a4dab8b65b27720452e3
»»»»» Script output:
42

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing de8b4315ca696f67f4086e8cadfaef655b680405
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/bcBztReMBo
Two terms in a row
at /tmp/bcBztReMBo:1
------> 42⏏ .say
    expecting any of:
        infix
        infix stopper
        statement end
        statement modifier
        statement modifier loop

»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 73836e1a70378b0c56c234e84385159564a0c355
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/bcBztReMBo
Two terms in a row
at /tmp/bcBztReMBo:1
------> 42⏏ .say
    expecting any of:
        infix
        infix stopper
        statement end
        statement modifier
        statement modifier loop

»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing be141b8d9bddc9798db6f11f70cdb117b7309526
»»»»» Script output:
42

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing db0c46e74491479a228f7da5570f5ca99b7618df
»»»»» Script output:
42

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing cb25b2f475f31335d77d018474482aceec2c74de
»»»»» Script output:
42

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
cb25b2f475f31335d77d018474482aceec2c74de is the first new commit
commit cb25b2f475f31335d77d018474482aceec2c74de
Author: TimToady <larry@wall.org>
Date:   Sat Sep 26 23:01:22 2015 -0700

    Allow infix:<.> if next thing is alphabetic
    
    As much as I mistrust "fluent" programming, we already have an infix:<.=>
    operator, so it's not a big stretch to have infix:<.>.  We limit it
    to actual method names so that we can detect (most) accidental use
    of P5's use of . for concatenation.  Note that this is a term/infix
    distinction now, so .meth where a term is expected still defaults to $_.
    Community standards for method cascades will likely ask for whitespace
    around infix:<.> to make a visual disinction from the term form, but we
    don't enforce that, if for no other reason than to refrain from giving
    the fluent programmers something to yammer on about.  Basically, I've
    decided that the slight possibility for greater confusion is outweighed
    by consistency with .= and utility of have a . that can also serve as
    a precedence modifier.  (Since both .= and . parse leftward with
    item assignment precedence, but rightward as a term.)

:040000 040000 be07c9752378c7034bc8d1ab2b34c78903ae1029 b09e45504a167da4e8328131c80bebac71267277 M	src