#998: Recent parrot changes cause lots of Rakudo spectests to abort with status
11
---------------------+------------------------------------------------------
Reporter: moritz | Owner: whiteknight
Type: bug | Status: new
Priority: blocker | Milestone:
Component: core | Version: 1.5.0
Severity: release | Keywords:
Lang: | Patch:
Platform: linux |
---------------------+------------------------------------------------------
Changes (by whiteknight):
* owner: => whiteknight
Comment:
I dont know specifically, but I think that this issue is relating to the
inferior runloops problem. This is a complex problem where we have a
single control flow path, but spread across at least two runloops on the C
stack. The first runloop runs the program to completion, returns, and the
second "outer" runloop picks up executing in an inconsistent environment.
This is a known issue in Parrot that has been documented in a variety of
tickets for several years.
I do not know why these issues have become huge problems for Rakudo this
month. We do need more time to dig into the issue and see what recent
changes may have made this issue appear so much recently. I *think* we can
put together a workaround for it before the release, but I don't want to
make promises.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/998#comment:7>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
