bisectable6

query

sub Foo(uint32 :$bar) { say $bar }; Foo(:bar(4)) # RT #127813

result

Bisecting: 3180 revisions left to test after this (roughly 12 steps)
[f97d5c2aafc8427bfce1279438712e5f34498a4d] implement "next" in whenever blocks
»»»»» Testing f97d5c2aafc8427bfce1279438712e5f34498a4d
»»»»» Script output:
4

»»»»» 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 998a1ef168efd57f3c4d3eb70e423ace01f6eeb0
»»»»» Script output:
Bytecode validation error at offset 40, instruction 6:
operand type 160 does not match register type 152
  in block <unit> at /tmp/4xoOHHpK2M line 1


»»»»» 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 0b973628ee202b79809140f797e1a8840fc64553
»»»»» Script output:
4

»»»»» 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 86d9e9123039b1d4b567186e0add168b2acfa44a
»»»»» Script output:
4

»»»»» 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 dc83730004d8a216c913a2c760690445cea5dc58
»»»»» Script output:
4

»»»»» 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 e4d538492ad0508a8be78f2032a1545f5f209017
»»»»» Script output:
Bytecode validation error at offset 40, instruction 6:
operand type 160 does not match register type 152
  in block <unit> at /tmp/4xoOHHpK2M line 1


»»»»» 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 54d43be48fddcb885ae8f2856dc536359ebed7d5
»»»»» Script output:
Bytecode validation error at offset 40, instruction 6:
operand type 160 does not match register type 152
  in block <unit> at /tmp/4xoOHHpK2M line 1


»»»»» 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 933e9a61c4479a41b993074d27036dfa32ef9a3f
»»»»» Script output:
4

»»»»» 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 92029524b41432faba15fe03287059e09e800991
»»»»» Script output:
4

»»»»» 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 1a16f6cdce904b50e8fd8d2bd375864986c79b4a
»»»»» Script output:
4

»»»»» 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 f5ed6be7866f9b125eba531bb05f91f494ce6597
»»»»» Script output:
Bytecode validation error at offset 40, instruction 6:
operand type 160 does not match register type 152
  in block <unit> at /tmp/4xoOHHpK2M line 1


»»»»» 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 b2511f549073878e872dbcaae4c2d004fd15b129
»»»»» Script output:
Bytecode validation error at offset 40, instruction 6:
operand type 160 does not match register type 152
  in block <unit> at /tmp/4xoOHHpK2M line 1


»»»»» 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 25e9fd76e85fabda20e263b6f87e27b0673f26e2
»»»»» Script output:
4

»»»»» 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”
»»»»» -------------------------------------------------------------------------
25e9fd76e85fabda20e263b6f87e27b0673f26e2 is the first new commit
commit 25e9fd76e85fabda20e263b6f87e27b0673f26e2
Author: Will "Coke" Coleda <will@coleda.com>
Date:   Fri Aug 19 09:31:24 2016 -0400

    update NQP revision to get MoarVM fixes

:040000 040000 5c6067bf95f3db48da248a17e03cbe23a2d8b26c c40a9905e7f604fbe4753401ee55e5a442b62324 M	tools