Ticket #1907 (closed bug: fixed)
Behavior of "exit" opcode changed since 2.11.0
Reported by: | coke | Owned by: | whiteknight |
---|---|---|---|
Priority: | critical | Milestone: | 3.0 |
Component: | core | Version: | master |
Severity: | high | Keywords: | |
Cc: | Language: | perl6 | |
Patch status: | applied | Platform: | all |
Description
This code:
.sub main :main exit 3 .end
until recently exited with no output. Recent versions of parrot carp about the line number the error occurred on.
After a incredibly painful bisect (due to the number of commits which resulted in a broken build), I narrowed it down to:
$ git bisect skip There are only 'skip'ped commits left to test. The first bad commit could be any of: 2483c6885910577821531e8da67f2f0c00f26775 6e591fa60048bfaae0d9cbc70176a69afcaec3fd 9d84c875231122af41405c44ea44a9a21f1c157a We cannot bisect more!
This change breaks a rakudo spectest.
Change History
Note: See
TracTickets for help on using
tickets.