Created
April 27, 2017 21:01
-
-
Save Whateverable/89ec676022df2fccafcc44bc838111fe to your computer and use it in GitHub Desktop.
bisectable6
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| 'BUTTERFLY'.parse-names |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Bisecting: 2047 revisions left to test after this (roughly 11 steps) | |
| [ca93ac9084d74a4e2e4bf7d247c230e8b1e39330] Fix for RT #129321 | |
| »»»»» Testing ca93ac9084d74a4e2e4bf7d247c230e8b1e39330 | |
| »»»»» Script output: | |
| Method 'parse-names' not found for invocant of class 'Str' | |
| in block <unit> at /tmp/QnPI_jBP0_ 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 471f4ba74da2dd2f4e657478004c9a80b8fcd498 | |
| »»»»» Script output: | |
| No such method 'parse-names' for invocant of type 'Str' | |
| in block <unit> at /tmp/QnPI_jBP0_ 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 3bf734f64425f4065f838667a5a7bf91f257ef0d | |
| »»»»» 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 7384939eb14767b63670e587b21e8bc2cb19fbab | |
| »»»»» Script output: | |
| No such method 'parse-names' for invocant of type 'Str' | |
| in block <unit> at /tmp/QnPI_jBP0_ 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 b61b3c7a7f0c6848f4698aaed23da21ca29115bc | |
| »»»»» Script output: | |
| No such method 'parse-names' for invocant of type 'Str' | |
| in block <unit> at /tmp/QnPI_jBP0_ 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 79d56708638dfa8c33aea0f694fc5de88878d337 | |
| »»»»» Script output: | |
| No such method 'parse-names' for invocant of type 'Str' | |
| in block <unit> at /tmp/QnPI_jBP0_ 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 cd47e2a806eb5387c60c24826ede37dc2bc9b722 | |
| »»»»» Script output: | |
| No such method 'parse-names' for invocant of type 'Str' | |
| in block <unit> at /tmp/QnPI_jBP0_ 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 e8167ec8519f3d493a9f83f1d40e4026bc68c52d | |
| »»»»» Script output: | |
| No such method 'parse-names' for invocant of type 'Str' | |
| in block <unit> at /tmp/QnPI_jBP0_ 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 84cf1d2fb3abc377ee9275582141a6bfbde53abe | |
| »»»»» 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 9d138b974affb9b05a370604114d9e48d4c8f3e6 | |
| »»»»» Script output: | |
| No such method 'parse-names' for invocant of type 'Str' | |
| in block <unit> at /tmp/QnPI_jBP0_ 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 164e393f179cdbc7853be479ea90808486fcfdec | |
| »»»»» Script output: | |
| No such method 'parse-names' for invocant of type 'Str' | |
| in block <unit> at /tmp/QnPI_jBP0_ 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 5c1761a6486317da6cef52bace348d3d5f350676 | |
| »»»»» 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” | |
| »»»»» ------------------------------------------------------------------------- | |
| 5c1761a6486317da6cef52bace348d3d5f350676 is the first new commit | |
| commit 5c1761a6486317da6cef52bace348d3d5f350676 | |
| Author: Zoffix Znet <cpan@zoffix.com> | |
| Date: Thu Mar 2 19:22:23 2017 +0000 | |
| Implement Str.parse-names | |
| Functionality: | |
| - similar to "\c[BELL, BLACK HEART SUIT]", except can be used by | |
| users at runtime, without requiring EVAL/nqp in user's code | |
| - Unlike \c[…] does not allow comments or anything similarly isoteric. | |
| The idea is this will process some sort of user input, so we want | |
| it just as liberal as necesary (whitespace around char names is allowed). | |
| Naming: | |
| - the name follows Str.parse-base that parses a string containing numerals | |
| in some base; whereas this routine parses a string of character names | |
| :040000 040000 45abf611f63dd4e5ca7772a7d6325fb2d1a1bc0b f517504299f366ca7791cd546e78d74a3ad668e6 M src | |
| :040000 040000 00a8ee2eff95255669fcf18a09fece43e4826b63 e475563156153b47efc3be7f3e0ac20e12aa52a8 M t |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment