No, sorry. I meant that I only tested for a couple minutes at each
commit.
Commits before the one bisect found never manifested the issue.
On 2017.10.16 10:52 am, jn...@jnthn.net via RT wrote:
> On Fri, 13 Oct 2017 10:13:36 -0700, jdv79 wrote:
>> The symptom is that sometimes (90%+ on my box and
No, sorry. I meant that I only tested for a couple minutes at each
commit.
Commits before the one bisect found never manifested the issue.
On 2017.10.16 10:52 am, jn...@jnthn.net via RT wrote:
On Fri, 13 Oct 2017 10:13:36 -0700, jdv79 wrote:
The symptom is that sometimes (90%+ on my box and un
On Sat, 08 Jul 2017 10:45:26 -0700, c...@zoffix.com wrote:
> Does it still happen after this commit
> https://github.com/rakudo/rakudo/commit/f6d4fbd24b ?
>
> I see you have a couple of `run`s in there which use Proc::Async under
> the hood.
Seems to fix it. Now I'm up against some other error
Note that running under MVM_SPESH_DISABLE=1 seems to elide the bug.
On 2017.02.01 01:01 pm, perl6 via RT wrote:
Greetings,
This message has been automatically generated in response to the
creation of a trouble ticket regarding:
"[BUG] [CONC] attribute from one role used in another via p
object isn't in P2 anymore
and "self" in PIR replaces it, what is the equivalent in pasm? That
looks like what's breaking the OO benches right now.
Thanks,
Justin DeVuyst
--- parrot/examples/benchmarks/vpm.imc 2004-12-13 03:00:24.0 -0500
+++ parrot_new/examples/
