Skip to content

Instantly share code, notes, and snippets.

@Whateverable
Created April 5, 2019 16:01
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/e261abca6d91d0fea89f81161eb4a89e to your computer and use it in GitHub Desktop.
Save Whateverable/e261abca6d91d0fea89f81161eb4a89e to your computer and use it in GitHub Desktop.
bisectable6
@*ARGS = <-a=42>; sub MAIN ( :@a ) { .say for @a }
Bisecting: 4740 revisions left to test after this (roughly 12 steps)
[055cf7570306f527985d3d3e86de34e6600cb310] We have signal in JVM; re-order and remove #?jvm.
»»»»» Testing 055cf7570306f527985d3d3e86de34e6600cb310
»»»»» Script output:
Usage:
/tmp/0rooGzBhQ5 [-a=<Positional>]
»»»»» Script exit code: 2
»»»»» Bisecting by exit code
»»»»» Current exit code is 2, exit code on “old” revision is 2
»»»»» 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 c43817ace0a644114e70c79a51cb9b312ff30d70
»»»»» Script output:
Usage:
/tmp/0rooGzBhQ5 [-a=<Positional>]
»»»»» Script exit code: 2
»»»»» Bisecting by exit code
»»»»» Current exit code is 2, exit code on “old” revision is 2
»»»»» 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 5fe0140cfd4dbacd3a696aaefedc8ad30e6a6269
»»»»» Script output:
Usage:
/tmp/0rooGzBhQ5 [-a=<Positional>]
»»»»» Script exit code: 2
»»»»» Bisecting by exit code
»»»»» Current exit code is 2, exit code on “old” revision is 2
»»»»» 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 72b896c8ee16d8384c5c76a7a151fefbb184c39e
»»»»» Script output:
Usage:
/tmp/0rooGzBhQ5 [-a=<Positional>]
»»»»» Script exit code: 2
»»»»» Bisecting by exit code
»»»»» Current exit code is 2, exit code on “old” revision is 2
»»»»» 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 4d7cdc0f415ac887a67c07a8dd5be5b29a36ec71
»»»»» Script output:
Usage:
/tmp/0rooGzBhQ5 [-a=<Positional>]
»»»»» Script exit code: 2
»»»»» Bisecting by exit code
»»»»» Current exit code is 2, exit code on “old” revision is 2
»»»»» 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 b92afb0b0a9bf8fa6b29ed7219a332d23ad91f9f
»»»»» Script output:
Usage:
/tmp/0rooGzBhQ5 [-a=<Positional>]
»»»»» Script exit code: 2
»»»»» Bisecting by exit code
»»»»» Current exit code is 2, exit code on “old” revision is 2
»»»»» 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 e0f84e05b4d9a8bfc3077e15a46fedbb8afdd90f
»»»»» Cannot test this commit. Reason: Commit exists, but a perl6 executable could not be built for it
»»»»» Therefore, skipping this revision
»»»»» -------------------------------------------------------------------------
»»»»» Testing ed29caaba76e185c82a303e53496583b1c01f324
»»»»» Script output:
Usage:
/tmp/0rooGzBhQ5 [-a=<Positional>]
»»»»» Script exit code: 2
»»»»» Bisecting by exit code
»»»»» Current exit code is 2, exit code on “old” revision is 2
»»»»» 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 b5843b0e3a1cc9037b59a3f630485af929311d37
»»»»» Script output:
42
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 2
»»»»» 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 17c9d88f281f1b73dfae590c19c72b7a3cdabbf1
»»»»» Script output:
Usage:
/tmp/0rooGzBhQ5 [-a=<Positional>]
»»»»» Script exit code: 2
»»»»» Bisecting by exit code
»»»»» Current exit code is 2, exit code on “old” revision is 2
»»»»» 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 4459364eeff0c3089548ab5833f30ff37fb60a26
»»»»» Script output:
Usage:
/tmp/0rooGzBhQ5 [-a=<Positional>]
»»»»» Script exit code: 2
»»»»» Bisecting by exit code
»»»»» Current exit code is 2, exit code on “old” revision is 2
»»»»» 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 0d47db86c62397809fbdb4ec7d909c92397e0ebd
»»»»» Script output:
42
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 2
»»»»» 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 87d219ee68f53855957f6f151fa9f88106ce7dfa
»»»»» Script output:
42
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 2
»»»»» 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 89b446770bb85127550b8fb9c3d67d9e736a3199
»»»»» Script output:
Usage:
/tmp/0rooGzBhQ5 [-a=<Positional>]
»»»»» Script exit code: 2
»»»»» Bisecting by exit code
»»»»» Current exit code is 2, exit code on “old” revision is 2
»»»»» 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”
»»»»» -------------------------------------------------------------------------
87d219ee68f53855957f6f151fa9f88106ce7dfa is the first new commit
commit 87d219ee68f53855957f6f151fa9f88106ce7dfa
Author: Elizabeth Mattijsen <liz@wenzperl.nl>
Date: Tue Mar 26 18:52:58 2019 +0100
Make a single named param match @ sig in MAIN
Fixes R#2797. This does **not** rewrite the signature binder. Instead,
if the generated capture can not find any candidates, the capture changes
any named scalar values into 1 element arrays, and tries to find candidates
again. If that is succesful, the modified signature is dispatched.
This is really a hack, but will in most cases do the right.
:040000 040000 e226c0622bba8704016f0bb47a3c666fd697ed53 9eea2605c49901b310c187fad6afef3f033330b5 M src
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment