| IRC logs at
Set by AlexDaniel on 12 June 2018.
01:32 sena_kun left 01:48 sena_kun joined 03:32 sena_kun left 03:48 sena_kun joined 05:34 sena_kun left 05:48 sena_kun joined
nwc10 jnthn: it's pretty calm here. The fun is forecast to arrive in 4.5 hours, and it's surprising how little evidence there is of it yet 06:29
06:51 domidumont joined 07:06 domidumont left 07:33 sena_kun left 07:48 sena_kun joined 08:27 zakharyas joined 08:44 moon-child left 08:51 moon-child joined 09:10 domidumont joined 09:31 sena_kun left 09:44 domidumont left 09:48 sena_kun joined 09:49 domidumont joined
jnthn It was very windy/wet here overnight. Then bizzarely I just walked to work in the sun. 09:52
moritz_ we quarter-hour stretches of sun here, and then it's all grey and windy and rainy again 10:08
10:08 moritz_ is now known as moritz 10:53 zakharyas left 10:56 zakharyas joined 11:08 domidumont left
nwc10 The fun started here about 10 minutes ago 11:18
jnthn I'm not sure if we had our share of fun overnight, or if it was just the appetizer... 11:19
timotimo we certainly had rattling and whistling 11:25
11:33 sena_kun left 11:48 sena_kun joined 11:50 zakharyas left 12:00 Guest4508 joined 12:47 patrickb joined
Guest4508 I wonder if I should report the "Corrupt multi dispatch cache" bug 13:00
at least we have a 100% reproducible case even though one might have to wait for it to trigger 13:01
here's the code in case anyone is interested: 13:02
while ./perl6-m -Ilib t/spec/S17-promise/lock-async-stress2.t; do :; done 13:03
sena_kun Guest4508: is thee any reason _not_ to report it? 13:07
I mean, if there is a fatal bug with steps to reproduce related to our basic test suite, what can be reasons not to report it? :) 13:08
timotimo implementorture 13:09
Guest4508 sena_kun: I didn't want to stress out jnthn :) 13:11
but of course I'll report it
13:15 vesper11 left, vesper joined 13:25 zakharyas joined 13:32 zakharyas left 13:34 sena_kun left 13:37 zakharyas joined 13:47 sena_kun joined
nine -win 10 13:51
nwc10 nine: US vs AT keyboard layout? (your fingers thought US, but the OS thought AT) 13:59
lizmat Guest4508 jnthn confirmed on MacOS on HEAD in the 95th run 14:09
MoarVM panic: Corrupt multi dispatch cache: cur_node != 0, re-check == 0x0
jnthn 95th /o) 14:13
timotimo i recommend rr record if you can reproduce it on linux 14:19
repeat until it crashes, make sure to delete recordings in between runs, though
and not to delete the recording after the crash :D
oh, i think you can pass a directory that it'll use, with an env var maybe? 14:20
14:28 lucasb joined
lizmat jnthn: 2nd time I tried, it died at the 53rd try 14:35
Guest4508 lizmat: rr doesn't work on Ryzen cpu's if you happen to have one 14:37
lizmat is on MacOS
Guest4508 jnthn: if you're utterly bored, this is what I managed to dig out wrt the 'Corrupt multi dispatch' error 14:39
jnthn Not that bored, alas ;) 14:45
I think I might well have investigated this one before to no avail
And I'm quite sure today isn't one of my smarter-than-average days :)
14:45 domidumont joined
Guest4508 :) 14:48
moritz today is my "the answer, my friend, is blowing in the wind" day :-) 14:49
jnthn Only trouble is spotting it among all the *other* things blowing in the wind... 14:52
lizmat fwiw, upping the number of threads to 12, seems to make it crash sooner (29th attempt) 15:01
nine nwc10: yes. I use application specific keyboard layouts. US for terminal (where I do all my coding and IRC) and AT for the rest (i.e. writing emails in German). Sometimes after a reboot KDE forgets the application specific setting 15:16
15:33 sena_kun left
lizmat fwiw: upping the number of threads to 64 makes it a lot slower, and I haven't seen it crash yet 15:43
(running for ~ hour now)
15:49 sena_kun joined 15:56 domidumont left 16:08 patrickb left 16:44 zakharyas left
lizmat and running for another hour without fail, stopped now 16:52
it's that time of the week again: another Rakudo Weekly News hits the Net: 17:09
jnthn lizmat++ 17:23
17:32 sena_kun left 17:47 sena_kun joined 18:18 Kaiepi left 18:23 Kaiepi joined 18:26 Kaiepi left 18:29 Kaiepi joined 18:31 Kaiepi left, Kaiepi joined 18:46 Ven`` joined 18:59 vrurg left 19:00 vrurg joined 19:04 vrurg left 19:14 Ven`` left 19:19 domidumont joined 19:29 bartolin joined 19:32 sena_kun left 19:46 sena_kun joined 20:10 vrurg joined 20:12 domidumont left, vrurg_ joined 20:15 vrurg left, vrurg_ left 20:16 Kaiepi left 20:17 vrurg_ joined 20:18 Kaiepi joined 20:20 Kaiepi left, Kaiepi joined 21:08 vrurg_ left 21:10 Ven`` joined 21:32 sena_kun left 21:47 sena_kun joined 22:13 Kaiepi left 22:14 Kaiepi joined 22:15 Kaiepi left 22:20 Kaiepi joined 22:30 Kaiepi left 22:31 Kaiepi joined 23:04 Ven`` left 23:06 Ven`` joined 23:08 Ven`` left 23:33 sena_kun left 23:46 vrurg joined 23:47 sena_kun joined 23:51 vrurg left