github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm
Set by AlexDaniel on 12 June 2018.
nwc10 Good *, #moarvm 08:09
dogbert11 not much going on here it seems, could it be the heat? 14:17
lizmat dogbert11: that'd be one thing 14:47
people being busy with other stuff because of having been on holiday / going to be on holiday
may be another
dogbert11 lizmat: it's 29 degrees where I'm at and it's a bit too much for me 14:52
lizmat inside or outside ? :-)
25.6 here, inside :-)
dogbert11 same temp both inside and outside :( 14:55
lizmat ah, outside it's still a bit hotter here, 29 or so 15:00
dogbert11 guess you're staying inside until it cools down a bit then 15:01
lizmat yeah... although the heat of my notebook is pushing me out already :-) 15:02
spectests don't help in these circumstances :-)
dogbert11 I can imagine :-) 15:42
dogbert11 are messages like this suspect or totally ok? 18:09
Thread 6 pushed to an object (NQPArray) allocated by thread 3
at gen/moar/stage2/nqpmo.nqp:1414 (/home/dogbert/repos/rakudo/install/share/nqp/lib/nqpmo.moarvm:mixin)
from gen/moar/Grammar.nqp:60 (/home/dogbert/repos/rakudo/blib/Perl6/Grammar.moarvm:unbalanced)
MasterDuke without being 100% sure i would think that's ok. the gc could cause things to move between threads, right? 19:16
nine No, the owner of an object will stay the same 19:48
It's not a sign that something goes wrong. It may help finding unsafe threading code but I'd consider it a weak indication only (without having looked at the actual code) 19:49
dogbert11 nine, MasterDuke: it's the output from: MVM_CROSS_THREAD_WRITE_LOG=1 MVM_SPESH_DISABLE=1 ./perl6-m -e "await (^250).map({ start { EVAL '/0|1|2/' } }); say 'ok'" 20:35
the code has just failed with a random error message in this case: ===SORRY!=== Local '__lowered_param__82' already declared 20:38
I took the code snippet from github.com/Raku/old-issue-tracker/issues/4507 20:40