Skip to content

Instantly share code, notes, and snippets.

@Whateverable
Created March 11, 2017 00:16
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/fec92f7b9b24bf06df78e42fad21c13a to your computer and use it in GitHub Desktop.
Save Whateverable/fec92f7b9b24bf06df78e42fad21c13a to your computer and use it in GitHub Desktop.
bisectable6
old=4a295dc5 $++ for '/home/bisectable/.bash_history'.IO.lines.rotor(30, :partial)
Bisecting: 229 revisions left to test after this (roughly 8 steps)
[1bb7da99453a8ccec351c4d29651121cfee4c559] Merge branch 'nom' into braids
»»»»» Testing 1bb7da99453a8ccec351c4d29651121cfee4c559
»»»»» Cannot test this commit. Reason: Commit exists, but a perl6 executable could not be built for it
»»»»» Therefore, skipping this revision
»»»»» -------------------------------------------------------------------------
»»»»» Testing e5ca5c278c7a67a4613c27b354853849df3082cc
»»»»» Script output:
readline requires an object with REPR MVMOSHandle
in block <unit> at /tmp/f67gkFYus4 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 4b18a8b7e3f8ace30b9579ede30f2914bbe414d5
»»»»» Cannot test this commit. Reason: Commit exists, but a perl6 executable could not be built for it
»»»»» Therefore, skipping this revision
»»»»» -------------------------------------------------------------------------
»»»»» Testing e8167ec8519f3d493a9f83f1d40e4026bc68c52d
»»»»» 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 048c81d39dd71d8039a653dc2a0b9d96f5ab1341
»»»»» 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 b9d9279a6d2aff68791b8085d8e09678886026bb
»»»»» 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 00e60d94803f6d58e1fb6228d0fc24ee406ccc63
»»»»» 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 ede01c24766def69e0740b5e19e7b48789cbded8
»»»»» 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 ec5dad5e292cad082da5b8213da04fee2d55ceef
»»»»» Script output:
readline requires an object with REPR MVMOSHandle
in block <unit> at /tmp/f67gkFYus4 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 ae9d517853b5f9ce7f710d6c1d7690d5e8f0c71a
»»»»» Script output:
readline requires an object with REPR MVMOSHandle
in block <unit> at /tmp/f67gkFYus4 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 dd6c7b646652399a8239193206cf993a517f7a1c
»»»»» Script output:
readline requires an object with REPR MVMOSHandle
in block <unit> at /tmp/f67gkFYus4 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 2734533a05e3ef15fd9b5954b58ecd216a5ee92e
»»»»» Script output:
readline requires an object with REPR MVMOSHandle
in block <unit> at /tmp/f67gkFYus4 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”
»»»»» -------------------------------------------------------------------------
ede01c24766def69e0740b5e19e7b48789cbded8 is the first new commit
commit ede01c24766def69e0740b5e19e7b48789cbded8
Author: Zoffix Znet <cpan@zoffix.com>
Date: Fri Jan 27 14:09:33 2017 +0000
Fix crash in .pull-one on IO::Handle.lines iterator
That seems to occur with RI::Batch/RI::Rotor iterators or
when .pull-one is called manually.
The iterator calls .get() on the Handle that reads from its $!PIO
and when that's exhaused the $!PIO is set to null. So when the next
.pull-one is done, we try to .get() on a closed handle by attempting
to read from nqp::null() that $!PIO is now is.
Bug find: https://irclog.perlgeek.de/perl6-dev/2017-01-27#i_13996365
:040000 040000 d22b9893877ac5aa293103c93af3e443b7233bbf 0617e318b722607ea65788d64c5a990f4753c10d M src
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment