Skip to content

Instantly share code, notes, and snippets.

@Whateverable

Whateverable/query

Created August 26, 2017 12:25
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/97d96022fdfed416e67ecadf5b2b9353 to your computer and use it in GitHub Desktop.
Save Whateverable/97d96022fdfed416e67ecadf5b2b9353 to your computer and use it in GitHub Desktop.
Download ZIP
bisectable6
Raw
query
await do for ^20 { start dir("/").eager }
Raw
result
Bisecting: 2661 revisions left to test after this (roughly 11 steps)
[a98724262c4db0ab6bafec2281e00081b137b019] Merge pull request #940 from samcv/nqpbump
»»»»» Testing a98724262c4db0ab6bafec2281e00081b137b019
»»»»» Script output:
===SORRY!===
Type check failed in binding; expected Str but got Mu (Mu)
»»»»» 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 c630548c6ef4be8235c92e74e80db69a1172fc49
»»»»» Script output:
Tried to get the result of a broken Promise
in block <unit> at /tmp/Lk8ldw9AnX line 1
Original exception:
Type check failed in binding; expected Str but got Mu (Mu)
in code at /tmp/Lk8ldw9AnX 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 b22383fe62fa1a112c8fb019b2b778cd258fad79
»»»»» Script output:
Tried to get the result of a broken Promise
in block <unit> at /tmp/Lk8ldw9AnX line 1
Original exception:
Type check failed in binding; expected Str but got Mu (Mu)
in code at /tmp/Lk8ldw9AnX 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 73c3bcc662bbca360163f3ff27bd517aa25ca2fb
»»»»» Script output:
Tried to get the result of a broken Promise
in block <unit> at /tmp/Lk8ldw9AnX line 1
Original exception:
Type check failed in binding; expected Str but got Mu (Mu)
in code at /tmp/Lk8ldw9AnX 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 e0d108bfc8b447b47a6177ad0625acf619faef9e
»»»»» Script output:
Tried to get the result of a broken Promise
in block <unit> at /tmp/Lk8ldw9AnX line 1
Original exception:
Type check failed in binding; expected Str but got Mu (Mu)
in code at /tmp/Lk8ldw9AnX 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 01b6d3f56e9511071ed55ebedf50151542a616f4
»»»»» Cannot test this commit. Reason: Commit exists, but a perl6 executable could not be built for it
»»»»» Therefore, skipping this revision
»»»»» -------------------------------------------------------------------------
»»»»» Testing 591f69af1e05d6812172fe11eb2490e4bdc06781
»»»»» 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 84d052a01296f233a6078397a4f3464cf58340fa
»»»»» Script output:
Tried to get the result of a broken Promise
in block <unit> at /tmp/Lk8ldw9AnX line 1
Original exception:
Type check failed in binding; expected Str but got Mu (Mu)
in code at /tmp/Lk8ldw9AnX 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 76af17a8b1dc79f8923109bbd284afed2e2fe011
»»»»» Script output:
Tried to get the result of a broken Promise
in block <unit> at /tmp/Lk8ldw9AnX line 1
Original exception:
Type check failed in binding; expected Str but got Mu (Mu)
in code at /tmp/Lk8ldw9AnX 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 a3c71e7d39cbee42c8c89a74801bdcf48f1dbb78
»»»»» Script output:
Tried to get the result of a broken Promise
in block <unit> at /tmp/Lk8ldw9AnX line 1
Original exception:
Type check failed in binding; expected Str but got Mu (Mu)
in code at /tmp/Lk8ldw9AnX 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 2b8115f0e90267488349ca5865cc906c329ff94a
»»»»» 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 231cb3f5fe8f024ce1a3694560a4cf50ec570b9d
»»»»» 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 29e41b45fa809391d0bf749efe00a62592bbe492
»»»»» Script output:
Tried to get the result of a broken Promise
in block <unit> at /tmp/Lk8ldw9AnX line 1
Original exception:
Required named argument 'path' not passed
in code at /tmp/Lk8ldw9AnX 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”
»»»»» -------------------------------------------------------------------------
231cb3f5fe8f024ce1a3694560a4cf50ec570b9d is the first new commit
commit 231cb3f5fe8f024ce1a3694560a4cf50ec570b9d
Author: Jonathan Worthington <jnthn@jnthn.net>
Date: Tue Aug 15 00:35:52 2017 +0200
Fix bad assumption about methods being closures.
They're not, since they're looked up via a table in the meta-object.
Thus this could cause data races when paths were being manipulated
from different threads.
:040000 040000 030caa31c16371f0bf98577dec106510328526de 7d78a2698669c008facc52650b15ef5aa9459027 M src
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment