Skip to content

Instantly share code, notes, and snippets.

@Whateverable
Created October 10, 2016 21:35
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/667d94f78e80294dd408e5f26c97010b to your computer and use it in GitHub Desktop.
Save Whateverable/667d94f78e80294dd408e5f26c97010b to your computer and use it in GitHub Desktop.
bisectable6
sub t { say $*d }; my $*d = 1; await do { start { t() } }
Bisecting: 1070 revisions left to test after this (roughly 10 steps)
[0a16ed597d6e91a6333f766050e8edbda6c122cd] always mark enum expression as wanted
»»»»» Testing 0a16ed597d6e91a6333f766050e8edbda6c122cd
»»»»» Script output:
Dynamic variable $*d not found
in block <unit> at /tmp/LmAO8qTTwT 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 fa84f134400977bd01dd01355fed679a3ac636e8
»»»»» Script output:
Dynamic variable $*d not found
in block <unit> at /tmp/LmAO8qTTwT 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 a87fc7d0bcff5166b4c4298f1312ba5fcea745cc
»»»»» Script output:
1
»»»»» 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 c732485e740b74d4268f3f60a7636a768d686f63
»»»»» Script output:
Dynamic variable $*d not found
in block <unit> at /tmp/LmAO8qTTwT 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 d43ea0703261683b78fee0da934753363180aa26
»»»»» Script output:
1
»»»»» 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 b00e9c4dcd87bed486e198ad4c5924091b850da0
»»»»» Script output:
1
»»»»» 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 2e963dfc0a8668d59dda473d0e8dcfe6ce9f8ca3
»»»»» Script output:
1
»»»»» 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 079da99281365804a362036e9bdd0fa30bb5d2f1
»»»»» Script output:
1
»»»»» 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 b2511f549073878e872dbcaae4c2d004fd15b129
»»»»» Script output:
Dynamic variable $*d not found
in block <unit> at /tmp/LmAO8qTTwT 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 1a16f6cdce904b50e8fd8d2bd375864986c79b4a
»»»»» Script output:
1
»»»»» 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 25e9fd76e85fabda20e263b6f87e27b0673f26e2
»»»»» Script output:
1
»»»»» 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment