bisectable6

query

old=2022.02 say grammar A { token TOP { <.print>+ } }.parse("foo")

result

Bisecting: 1684 revisions left to test after this (roughly 11 steps)
[a815b5ca1275c15126581c3733510cbbba31fbb8] Merge pull request #5157 from vrurg/rakuast-lang-version
»»»»» Testing a815b5ca1275c15126581c3733510cbbba31fbb8
»»»»» Script output:
Cannot resolve caller print(Mu:U: A:D); none of these signatures matches:
    (Mu: *%_)
  in block <unit> at /tmp/ZzLnmmLCQc 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 ec622b9366f25c6a32dd47b9cdda7fbd1a177be9
»»»»» Script output:
Cannot resolve caller print(Mu:U: A:D); none of these signatures matches:
    (Mu: *%_)
  in block <unit> at /tmp/ZzLnmmLCQc 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 5e10f2956474873fc3f00a6c53a1b82d67346af2
»»»»» Script output:
Cannot resolve caller print(Mu:U: A:D); none of these signatures matches:
    (Mu: *%_)
  in block <unit> at /tmp/ZzLnmmLCQc 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 ca1f20c92dfc6e4e4dc46ced95f372e7454b6458
»»»»» Script output:
Cannot resolve caller print(Mu:U: A:D); none of these signatures matches:
    (Mu: *%_)
  in regex TOP at /tmp/ZzLnmmLCQc line 1
  in block <unit> at /tmp/ZzLnmmLCQc 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 4ef932fd9586d594eb68be2ad63f3b4da096610b
»»»»» Script output:
Cannot resolve caller print(Mu:U: A:D); none of these signatures matches:
    (Mu: *%_)
  in regex TOP at /tmp/ZzLnmmLCQc line 1
  in block <unit> at /tmp/ZzLnmmLCQc 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 c0b19bec554e6c325c8710ef468a89608fc54af1
»»»»» Script output:
Cannot resolve caller print(Mu:U: A:D); none of these signatures matches:
    (Mu: *%_)
  in regex TOP at /tmp/ZzLnmmLCQc line 1
  in block <unit> at /tmp/ZzLnmmLCQc 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 165261853710adaa92a4904e0c480937565f8078
»»»»» Script output:
｢foo｣

»»»»» 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 6d90c9230a778be683257224c54a929c47b21943
»»»»» Script output:
｢foo｣

»»»»» 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 9438ef1a795dac14262432c23a18d5200ff5af54
»»»»» Script output:
Cannot resolve caller print(Mu:U: A:D); none of these signatures matches:
    (Mu: *%_)
  in regex TOP at /tmp/ZzLnmmLCQc line 1
  in block <unit> at /tmp/ZzLnmmLCQc 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 a9da976e8820ed02d53fbec74eb9b3d3dd9a7a65
»»»»» Script output:
Cannot resolve caller print(Mu:U: A:D); none of these signatures matches:
    (Mu: *%_)
  in regex TOP at /tmp/ZzLnmmLCQc line 1
  in block <unit> at /tmp/ZzLnmmLCQc 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 bd2c719ed4126a5738cda52e114906accf6d9b3c
»»»»» Script output:
｢foo｣

»»»»» 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 349ee9c225ee125437278c9808474f3c4a81b475
»»»»» Script output:
Cannot resolve caller print(Mu:U: A:D); none of these signatures matches:
    (Mu: *%_)
  in regex TOP at /tmp/ZzLnmmLCQc line 1
  in block <unit> at /tmp/ZzLnmmLCQc 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”
bd2c719ed4126a5738cda52e114906accf6d9b3c is the first new commit
commit bd2c719ed4126a5738cda52e114906accf6d9b3c
Author: Elizabeth Mattijsen <liz@raku.rocks>
Date:   Fri Nov 10 20:12:26 2023 +0100

    Make sure that "no actions" really means it
    
    Putting a Raku Mu object in the actions of a grammar by default,
    is telling NQP that it should look in the Raku Mu class, of which
    we have many, and one of them is called "print".  Which causes
    issue #5443.
    
    This commit makes sure we store an nqp::null in the grammar's
    $!actions attribute, indicating to the matching logic that there
    are **NO** actions to be executed.
    
    Fixes #5443.  And should probably also positively affect performance
    of grammars used without an action class.

 src/core.c/Grammar.rakumod | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)