🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm
Set by lizmat on 8 June 2022.
05:37 lizmat_ joined 05:41 lizmat left 09:46 Geth joined 10:39 sjm_ left 16:35 rakkable left 16:36 rakkable joined
nine Is there any progress on make install with RakuAST? 19:02
[Coke] Haven't seen any; nine, should bootstrap-rakuast build? (just tried a checkout, it was happy with the existing nqp/moar, but then died with An exception X::Comp::AdHoc occurred while evaluating a BEGIN: 19:51
(before install)
(during build) 19:53
nuking nqp/moar, trying again 19:54
timo how long do i run nqp tests in serial to figure out if maybe the segfault happens only if nqps are run in parallel ... 20:06
nine [Coke]: I see a similar failure here 20:13
[Coke] timo: it's using prove, right? TEST_JOBS=1 20:16
nine [Coke]: oh, sorry, false alarm. Build went fine. You are running it with RAKUDO_RAKUAST=1 make, right? 20:17
timo i'm using -j1 20:19
[Coke] nine: ah, no, I wrongly assumed it was defaulted on in the branch. my bad. 20:21
timo: that should do it (if you're running prove and not 'make test') 20:22
timo yeah, that's what i'm doing 20:43
the question was something else though
hm, i don't actually have like a counter running though 20:59
21:43 finanalyst left
timo hum. but it also crashed compiling a part of Rakudo during its build. and that's not very multithreaded right? so maybe parallelism can't be the cause, only make it more likely to show for some reason? 22:01
but also that was on mipsel rather than armel i think 22:02
i'll let it go over night just to be sure … 23:00