Skip to content

Instantly share code, notes, and snippets.

@Whateverable
Created September 10, 2017 17:14
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save Whateverable/3bfbdd10905aafbb93b7a468297bc96b to your computer and use it in GitHub Desktop.
Save Whateverable/3bfbdd10905aafbb93b7a468297bc96b to your computer and use it in GitHub Desktop.
bisectable6
old=2014.01 say '123' ~~ / :my $a=2; <{ '$a' }> /;
Bisecting: 6326 revisions left to test after this (roughly 13 steps)
[5ffd01f33bc60ba757fe4a10d634b06715ec739b] allow traits to join the $*BORG
»»»»» Testing 5ffd01f33bc60ba757fe4a10d634b06715ec739b
»»»»» Script output:
「2」
»»»»» 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 c7b9340e88bf1ba2baa3d8b2d723c5b6e297facb
»»»»» Script output:
===SORRY!=== Error while compiling EVAL_0
Variable '$a' is not declared
at EVAL_0:1
------> anon regex { ^$a⏏}
»»»»» 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 680fe58c1433f7df81ad8e8a84c57636a92df21c
»»»»» Script output:
Unhandled exception: Cannot assign to an immutable value
at <unknown>:1 (/tmp/whateverable/rakudo-moar/680fe58c1433f7df81ad8e8a84c57636a92df21c/share/perl6/runtime/CORE.setting.moarvm:print_exception:4294967295)
from src/gen/m-CORE.setting:16427 (/tmp/whateverable/rakudo-moar/680fe58c1433f7df81ad8e8a84c57636a92df21c/share/perl6/runtime/CORE.setting.moarvm:<anon>:40)
from gen/moar/stage2/NQPHLL.nqp:1420 (/tmp/whateverable/rakudo-moar/680fe58c1433f7df81ad8e8a84c57636a92df21c/share/nqp/lib/NQPHLL.moarvm:command_eval:380)
from src/Perl6/Compiler.nqp:59 (/tmp/whateverable/rakudo-moar/680fe58c1433f7df81ad8e8a84c57636a92df21c/share/nqp/lib/Perl6/Compiler.moarvm:command_eval:93)
from gen/moar/stage2/NQPHLL.nqp:1360 (/tmp/whateverable/rakudo-moar/680fe58c1433f7df81ad8e8a84c57636a92df21c/share/nqp/lib/NQPHLL.moarvm:command_line:114)
from src/gen/m-main.nqp:39 (/tmp/whateverable/rakudo-moar/680fe58c1433f7df81ad8e8a84c57636a92df21c/share/perl6/runtime/perl6.moarvm:MAIN:18)
from src/gen/m-main.nqp:35 (/tmp/whateverable/rakudo-moar/680fe58c1433f7df81ad8e8a84c57636a92df21c/share/perl6/runtime/perl6.moarvm:<mainline>:197)
from <unknown>:1 (/tmp/whateverable/rakudo-moar/680fe58c1433f7df81ad8e8a84c57636a92df21c/share/perl6/runtime/perl6.moarvm:<main>:8)
from <unknown>:1 (/tmp/whateverable/rakudo-moar/680fe58c1433f7df81ad8e8a84c57636a92df21c/share/perl6/runtime/perl6.moarvm:<entry>:9)
»»»»» 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 fb9f788fed0934ad369f01c48e58c7d4ea55c6ea
»»»»» Script output:
「2」
»»»»» 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 817767b70ded72a9e028bd00e2a83055e92f5433
»»»»» Script output:
»»»»» 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 5679420d703fd06d0a07eeb4d91e1608c44a7649
»»»»» Script output:
「2」
»»»»» 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 2d98c6239075ef199cda9e130fcbd21582c1a254
»»»»» Script output:
「2」
»»»»» 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 55850a3593ef2662bc17d2a232ef5dace391b62c
»»»»» Script output:
「2」
»»»»» 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 6d8768fb6367e5d6de727de08d012c5e5c9286f7
»»»»» Script output:
sort needs re-working after GLR
»»»»» 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 8ff2f5e3005586afb6eeff03be1c1748285bd7f9
»»»»» Script output:
sort needs re-working after GLR
»»»»» 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 a58bcae242456fac92080ae0160bfe5210b37aaf
»»»»» Script output:
「2」
»»»»» 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 306ff11d4974fd87af0e4556e02449a84f8939c7
»»»»» Script output:
sort needs re-working after GLR
in block <unit> at /tmp/EkFtJyZFn7: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 2f4291587b79135479ae0477295a5e8f6605e628
»»»»» Script output:
「2」
»»»»» 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 d2de5d654246b2945f41bc5e63e2248a90074e4f
»»»»» Script output:
sort needs re-working after GLR
in block <unit> at /tmp/EkFtJyZFn7: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”
»»»»» -------------------------------------------------------------------------
2f4291587b79135479ae0477295a5e8f6605e628 is the first new commit
commit 2f4291587b79135479ae0477295a5e8f6605e628
Author: jnthn <jnthn@jnthn.net>
Date: Thu Aug 13 15:24:50 2015 +0200
Get sort working again after GLR refactor.
Should be a decent bit more efficient too, though we can still do
better.
:040000 040000 4d9398c946ad45c9d60e814b5b19c655b0e910a4 7056f2f3f4f8ffc2669fd5e0dbb81251e8530cb7 M src
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment