bisectable6test

query

old=2017.05 new=2017.06 sub mem { "/proc/$*PID/statm".IO.lines[0].split(/\s/)[5] * 4096 / 1024 }; say mem(); run 'echo'; exit (mem() < 100000 ?? 1 !! 0);

result

Bisecting: 220 revisions left to test after this (roughly 8 steps)
[8f4f515f94187f0fb74972043e2edcaedf989700] Merge branch 'nom' into newer-cat-handle
»»»»» Testing 8f4f515f94187f0fb74972043e2edcaedf989700
»»»»» Script output:
58696

»»»»» 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 7fa8568254af94b0f9916c05069b683dc4fe0b1e
»»»»» Script output:
58716

»»»»» 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 b7150ae1adfcf810221b1ee9a7e3c73ec73c96f5
»»»»» Script output:
58768

»»»»» 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 3adb14af96fd231c6e789ea069a33827d3174d84
»»»»» Script output:
58724

»»»»» 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 ac31c5df465a13756fd0db3c22fb71f837a80e3e
»»»»» Script output:
58772

»»»»» 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 bf95bcb6c050bf7fbaa80d0754defc9d003fd072
»»»»» Script output:
58720

»»»»» 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 7c279f479fc475ff60fd690103a382b89350e4ad
»»»»» Script output:
58740

»»»»» 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 dc0e39b6211b86013e2f5e47531e8835eacb173c
»»»»» Script output:
58772

»»»»» 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 92bd7e4f54a92fa660f99b4d056d33a08fb98bd2
»»»»» Script output:
58772

»»»»» 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”
»»»»» -------------------------------------------------------------------------
92bd7e4f54a92fa660f99b4d056d33a08fb98bd2 is the first new commit
commit 92bd7e4f54a92fa660f99b4d056d33a08fb98bd2
Author: Jonathan Worthington <jnthn@jnthn.net>
Date:   Mon Jun 12 17:44:51 2017 +0200

    Re-implement Proc in terms of Proc::Async.
    
    Almost works; the case of chaining the output of one Proc into another
    is still to come.

:040000 040000 cc9bc09081a70ea1459acaa5a79cec109704def8 85131bb718a4da43b6418f13b969d4cf80773f5d M	src