Skip to content

Instantly share code, notes, and snippets.

@Whateverable
Created December 3, 2017 04: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/5b549d89bf73b4afafc27425d16e1b4a to your computer and use it in GitHub Desktop.
Save Whateverable/5b549d89bf73b4afafc27425d16e1b4a to your computer and use it in GitHub Desktop.
bisectable6
old=2016.10 new=2016.11 use v6;␤␤my $supply = supply {␤ die;␤}␤␤react {␤ whenever $supply {␤␤ }␤}␤CATCH { exit .gist.contains: ‘Original exception’ }
Bisecting: 158 revisions left to test after this (roughly 7 steps)
[ebcc33eb6fd450cc324714fbeb40aef9dc1b24ad] fix typo
»»»»» Testing ebcc33eb6fd450cc324714fbeb40aef9dc1b24ad
»»»»» Script output:
»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 0
»»»»» 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 0b5e38a16e7d3578949e9bb7e410b9b82c7876c3
»»»»» Script output:
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 0
»»»»» 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 ba152bdb96e35e60a4e2bac3c53eea2762f330a7
»»»»» Script output:
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 0
»»»»» 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 4539db45a1276fa758c507574ada60fbe3b09e9f
»»»»» Script output:
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 0
»»»»» 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 8064ff1b02ed05c2bfbcd957b74ded53c24cb0bb
»»»»» Script output:
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 0
»»»»» 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 7ba7eb4412ddddae0ec0546ee9265700090b533a
»»»»» Script output:
»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 0
»»»»» 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 abf6caf06eb7e48674d4e22a4ad6b580e5efecbf
»»»»» Script output:
»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 0
»»»»» 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 8c3e57d77e90fab1d504830bf69580f52e71a272
»»»»» Script output:
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 0
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
abf6caf06eb7e48674d4e22a4ad6b580e5efecbf is the first new commit
commit abf6caf06eb7e48674d4e22a4ad6b580e5efecbf
Author: Jonathan Worthington <jnthn@jnthn.net>
Date: Wed Nov 2 16:55:37 2016 +0100
Improve error reporting around broken promises.
Previously, we had the message of the original exception, together
with the backtrace of the await or .result call. Now, we:
* Clearly indicate that the exception was raised by obtaining the
result of a broken Promise
* Provide the location that this happened
* Provide the original exception's message
* Provide the backtrace of the original exception
:040000 040000 65844dd8a7d3ee05d39889e1081dd8361acc8631 fcdc0fe75b22d3f352e8a9ce8b960be8c3ef2f5c M src
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment