github.com/moarvm/moarvm | IRC logs at colabti.org/irclogger/irclogger_logs/moarvm
Set by AlexDaniel on 12 June 2018.
00:08 Kaiepi left, Kaiepi joined 00:09 p6bannerbot sets mode: +v Kaiepi 04:13 MasterDuke left 05:46 robertle left 05:59 huggable left, p6bannerbot left 06:03 lizmat left 07:02 domidumont joined 07:44 AlexDani` joined 07:48 AlexDaniel left 08:36 zakharyas joined 08:41 lizmat joined
nwc10 jnthn: paste.scsys.co.uk/582237 - that test case, wtih ASAN's excitement 08:43
I needed to set MVM_SPESH_BLOCKING=1
I can't currerntly build rakudo with MVM_SPESH_BLOCKING=1
and NQP fails 3 tests
08:49 robertle joined 09:09 zakharyas left 09:12 zakharyas joined
jnthn nwc10: Thanks 09:37
nwc10 I hope that the cause for both the bug tested here and the rakudo build failure turns out to be the same 09:45
10:09 AlexDani` is now known as AlexDaniel 10:13 brrt joined 10:18 AlexDaniel left, AlexDaniel joined 10:22 ChanServ sets mode: +vvvv brrt zakharyas robertle lizmat, ChanServ sets mode: +vv AlexDaniel domidumont
brrt \o 10:23
yoleaux 11 Nov 2018 10:59Z <nine> brrt: t/02-rakudo/12-proto-arity-count.t is failing occasionally with 'Register types do not match between value and node' at the end after all tests passed. Error goes away completely with MVM_SPESH_BLOCKING=1 which makes me believe that we're trying to JIT compile while already shutting down the VM.
brrt nine: noted
that is weird though
10:24 timewasteable6 joined, ChanServ sets mode: +o timewasteable6 10:40 domidumont left
dogbert17 brrt: there's a tad more info in M#992 but you've probably already seen that 10:41
synopsebot_ M#992 [open]: github.com/MoarVM/MoarVM/issues/992 [⚠ blocker ⚠] MVM_panic in t/02-rakudo/12-proto-arity-count.t
10:48 brrt left 11:59 zakharyas left 12:08 brrt joined, timewasteable6 sets mode: +v brrt 12:10 zakharyas joined 12:11 timewasteable6 sets mode: +v zakharyas 12:21 zakharyas left
brrt I guess I'll have to actually take a look one of these days 12:32
nwc10 brrt: or bribe jnthn -- nakup.itesco.cz/groceries/en-GB/sh.../beers/all 12:38
brrt or that. But I'm not sure it's ethical 12:44
13:04 brrt left 13:40 zakharyas joined, timewasteable6 sets mode: +v zakharyas 13:56 Kaiepi left, Kaiepi joined 13:57 timewasteable6 sets mode: +v Kaiepi 14:06 zakharyas left, zakharyas joined 14:07 timewasteable6 sets mode: +v zakharyas 14:11 domidumont joined 14:12 timewasteable6 sets mode: +v domidumont 14:54 Kaiepi left, Kaiepi joined 14:55 timewasteable6 sets mode: +v Kaiepi 15:05 zakharyas left 15:08 zakharyas joined, timewasteable6 sets mode: +v zakharyas 16:04 zakharyas left 16:07 zakharyas joined 16:08 timewasteable6 sets mode: +v zakharyas 16:23 domidumont left 16:27 brrt joined, timewasteable6 sets mode: +v brrt 16:35 Zoffix joined, timewasteable6 sets mode: +v Zoffix, ChanServ sets mode: +o Zoffix, p6bannerbot joined, timewasteable6 sets mode: +v p6bannerbot, ChanServ sets mode: +o p6bannerbot 16:36 Zoffix sets mode: +vvv timewasteable6 mst ChanServ 16:37 Zoffix left, buggable left, buggable joined, huggable joined, ZofBot left, ZofBot joined, timewasteable6 sets mode: +v ZofBot, p6bannerbot sets mode: +v ZofBot 16:38 SourceBaby joined, timewasteable6 sets mode: +v buggable, p6bannerbot sets mode: +v buggable, timewasteable6 sets mode: +v huggable, p6bannerbot sets mode: +v huggable, timewasteable6 sets mode: +v SourceBaby, p6bannerbot sets mode: +v SourceBaby
brrt Hmm. I kind of want to debug the issue you're all sending me. But I'm tired and have a bunch of $work. So it's not likely to be today 17:00
17:04 zakharyas left 17:06 zakharyas joined 17:07 timewasteable6 sets mode: +v zakharyas, p6bannerbot sets mode: +v zakharyas 17:13 timewasteable6 left 17:26 robertle_ joined 17:27 p6bannerbot sets mode: +v robertle_ 18:11 brrt left 18:12 brrt joined 18:13 p6bannerbot sets mode: +v brrt 18:19 Geth_ left, p6lert_ left, Geth joined, synopsebot_ left, p6lert joined, synopsebot joined, p6bannerbot sets mode: +v Geth, p6bannerbot sets mode: +v p6lert 18:20 p6bannerbot sets mode: +v synopsebot 19:00 zakharyas left 19:37 brrt left
nine .tell brrt scratch that idea of JITing while interp shutdown. We don't reach the end of MVM_interp_run and not even the FUDGED! message in t/spec/S06-advanced/callframe.rakudo.moar. But in all cases, we finish all tests. 20:16
yoleaux nine: I'll pass your message to brrt.
21:04 ZzZombo left 21:05 ZzZombo joined, p6bannerbot sets mode: +v ZzZombo 22:17 robertle_ left 22:48 MasterDuke joined, p6bannerbot sets mode: +v MasterDuke, MasterDuke left, MasterDuke joined, herbert.freenode.net sets mode: +v MasterDuke, p6bannerbot sets mode: +v MasterDuke 23:42 lizmat left