bisectable6

query

my $*TZ = 12345 andthen exit ($_ == DateTime.now.timezone ?? 1 !! 2)

result

Bisecting: 73 revisions left to test after this (roughly 6 steps)
[fa2013db402b99f8ebadf8ccb770b4ebeba3027e] Don't use "perl" in identifiers unless needed
»»»»» Testing fa2013db402b99f8ebadf8ccb770b4ebeba3027e
»»»»» Script output:

»»»»» Script exit code: 2
»»»»» Bisecting by exit code
»»»»» Current exit code is 2, 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 78f164517ce5f1d87e8ad75e7932b2963997eeac
»»»»» Script output:

»»»»» 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 2fe6420e87e5a08aacea1015c64d4a213ff46ed2
»»»»» Script output:

»»»»» Script exit code: 2
»»»»» Bisecting by exit code
»»»»» Current exit code is 2, 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 151fd310838b72f6d455cad1f54c9546a8793a98
»»»»» Script output:

»»»»» Script exit code: 2
»»»»» Bisecting by exit code
»»»»» Current exit code is 2, 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 ccc50f7ae62a4e23eb1aff33b94c23f075ef3277
»»»»» Script output:

»»»»» 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 613da571e85a089ccc22c65bccabaca250b87b81
»»»»» Script output:

»»»»» Script exit code: 2
»»»»» Bisecting by exit code
»»»»» Current exit code is 2, 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 7176cbc35756e6331da8f79b00d4dfd1cd700824
»»»»» Script output:

»»»»» 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”
613da571e85a089ccc22c65bccabaca250b87b81 is the first new commit
commit 613da571e85a089ccc22c65bccabaca250b87b81
Author: Elizabeth Mattijsen <liz@wenzperl.nl>
Date:   Mon Nov 2 17:53:12 2020 +0100

    Fix an issue with $*TZ and long-running processes
    
    This was spotted in production recently: before this commit, $*TZ
    was being set *once* on the first access to $*TZ.  If a long running
    process would cross a DST change, it would report the wrong value
    after that change.
    
    After this commit, $*TZ will be checked once an hour.  If it is set
    explicitely, it will *not* be checked henceforth.
    
    Moved the DST logic from Rakudo::Internals to DateTime, as to allow
    the logic to live in a locally accessible sub.

:040000 040000 f1ea59ce520a58696a2ea391b91662f231d1d109 9a9192c8f8f10b390201e25f0f4f56c29eed0739 M	src