Skip to content

Instantly share code, notes, and snippets.

@Whateverable
Created November 28, 2019 19:36
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/f13bd0d8f43e344a6450705bd43dbb3b to your computer and use it in GitHub Desktop.
Save Whateverable/f13bd0d8f43e344a6450705bd43dbb3b to your computer and use it in GitHub Desktop.
bisectable6
2019.07.1,2019.11 https://gist.github.com/AlexDaniel/00198fac369062afb76cc35a435f70ef
Bisecting: 233 revisions left to test after this (roughly 8 steps)
[497c9e07186b5b7a700559d3fbd5cb1df71dccda] Merge branch 'master' of https://github.com/rakudo/rakudo into rakudo_3136
»»»»» Testing 497c9e07186b5b7a700559d3fbd5cb1df71dccda
»»»»» Script output:
7.1422823
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 42
»»»»» 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 74f2d3f4656d92e7c903bc4b345024de6a7326c5
»»»»» Script output:
6.72878766
»»»»» Script exit code: 42
»»»»» Bisecting by exit code
»»»»» Current exit code is 42, exit code on “old” revision is 42
»»»»» 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 ae7e77e75974349cb689f892b098e48d15d2c0d5
»»»»» Script output:
7.4865961
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 42
»»»»» 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 7e1062659fb638abfe2af1563c5b59c953f18bc5
»»»»» Script output:
7.5282461
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 42
»»»»» 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 d7829b775197a3a2b71711a87006b041c758e24a
»»»»» Script output:
7.41214153
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 42
»»»»» 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 ad51a3a267a9837c21559e19361cb9b5752b6116
»»»»» Script output:
8.454479
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 42
»»»»» 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 38aa128ca9d8fec34ccdf84c72c5ab41224d48ab
»»»»» Script output:
7.4968846
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 42
»»»»» 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 ae4ba74262b1155ddf57cd2bac1f3aaccfc1e47f
»»»»» Script output:
7.5234891
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 42
»»»»» 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”
ae4ba74262b1155ddf57cd2bac1f3aaccfc1e47f is the first new commit
commit ae4ba74262b1155ddf57cd2bac1f3aaccfc1e47f
Author: Vadim Belman <vrurg@lflat.org>
Date: Tue Aug 6 19:07:12 2019 -0400
Make every CORE compile with its respective language revision
This is a preparation work to assign language version to core classes.
I.e. PseudoStash.^ver would report back either `6.c` or `6.e` depending
from which CORE the class was imported.
:040000 040000 05571ca53afec49fe178d1202d7066adc12533a3 c27c13cb695f6c79de4cb5b695ccf35f66ea7018 M src
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment