bisectable6

query

old=2015.09 50 . say

result

Bisecting: 2534 revisions left to test after this (roughly 11 steps)
[e4a1b568cbf79cfa2875636101e7077371816cb2] Make Int.polymod between 1.2x and 1.7x faster
»»»»» Testing e4a1b568cbf79cfa2875636101e7077371816cb2
»»»»» Script output:
50
»»»»» 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 9b336d6356c755d0948d79cdbb3c9291a8f5ab74
»»»»» Script output:
50
»»»»» 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 bccb16dafbf3f92738c9471a8457d2ab919fb3fc
»»»»» Script output:
50
»»»»» 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 f254cd4fa00d398c3994a829c220760f0d2abd4b
»»»»» Script output:
50
»»»»» 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 2b04b50e906dc750a7130b976252713ef7492880
»»»»» Script output:
50
»»»»» 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 198f84f68c6f31aef080d5b30703790ce09d54e1
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/hjA6oS0YZu
Unsupported use of . to concatenate strings; in Perl 6 please use ~
at /tmp/hjA6oS0YZu:1
------> 50 . ⏏say
»»»»» 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 8c9be895a76ab6935782808a908b8407cb9b1093
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/hjA6oS0YZu
Unsupported use of . to concatenate strings; in Perl 6 please use ~
at /tmp/hjA6oS0YZu:1
------> 50 . ⏏say
»»»»» 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 d5a6e99bee73cac0490c6fb2b72092dd420b5e05
»»»»» Cannot test this commit. Reason: Commit exists, but a perl6 executable could not be built for it
»»»»» Therefore, skipping this revision
»»»»» -------------------------------------------------------------------------
»»»»» Testing 3b7d17dcc170d0bc4e56a806e5a0f3ed1103166c
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/hjA6oS0YZu
Unsupported use of . to concatenate strings; in Perl 6 please use ~
at /tmp/hjA6oS0YZu:1
------> 50 . ⏏say
»»»»» 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 0024b0a060bcaf37ba4638ed385362e80fb23c3c
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/hjA6oS0YZu
Unsupported use of . to concatenate strings; in Perl 6 please use ~
at /tmp/hjA6oS0YZu:1
------> 50 . ⏏say
»»»»» 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 db0c46e74491479a228f7da5570f5ca99b7618df
»»»»» Script output:
50
»»»»» 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 0132b654104259b26a2920fb9a89f545281bb9b3
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/hjA6oS0YZu
Unsupported use of . to concatenate strings; in Perl 6 please use ~
at /tmp/hjA6oS0YZu:1
------> 50 . ⏏say
»»»»» 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/hjA6oS0YZu
Unsupported use of . to concatenate strings; in Perl 6 please use ~
at /tmp/hjA6oS0YZu:1
------> 50 . ⏏say
»»»»» 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 cb25b2f475f31335d77d018474482aceec2c74de
»»»»» Script output:
50
»»»»» 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