02:11 JimmyZ joined 06:02 terrencehan joined 07:25 FROGGS joined 08:03 rurban_ joined 08:04 zakharyas joined 08:33 brrt joined
dalek arVM: 3ba2676 | jnthn++ | src/io/syncpipe.c:
Avoid a use-after-free.

This was a bug on all platforms, but it seems that OSX delivers events with timing that exposes the bug. Hopefully deals with the qqx crashes on OSX.
09:32
arVM: 5f9e2d0 | jnthn++ | src/io/syncpipe.c:
Fix a conditional mess-up on Windows.
JimmyZ so all bugs that only happened on OSX is that only OSX is 'use strcit;' :P 09:55
jnthn All tests successful. 09:58
Files=931, Tests=34116, 248 wallclock secs ( 7.58 usr 2.87 sys + 752.64 cusr 98.85 csys = 861.94 CPU)
Result: PASS
On OSX. \o/ 09:59
First time I've ever got that there. :)
jnthn bumps TEST_JOBS up tfrom 4 o 8 and has another go
Passes again...in 3 minutes. :) 10:02
So hardware.
Very core.
timotimo \o/ 10:04
hardcore
FROGGS I fear that I've introduced most of the things jnthn has to hunt down lately :o( 10:08
nwc10 FROGGS: that is a risk of being productive 10:09
one can say the same about me and core perl 5 bugs
FROGGS *g*
yeah, and well, I hopefully can say that I'm still able to learn things... so it is not hopeless 10:10
nwc10 I can't remember enough to successfully Google^WYahoo! it, but there's some parable about the employee who left, who was responsible for 50% of the bugs 10:11
because, it turned out, he was also resposnbile for 75% of the progress
I didn't quite phrase that right - he did most of the work, and his bug *rate* was actually lower than the other employees
JimmyZ All tests successful? I can't get this on linux :( 10:14
nwc10 I have a TODO passing
jnthn JimmyZ: Really? What do you have failing?
nwc10 and a (maybe) 25% ASAN failure from a thread test 10:15
which I'd not mentioned before
seems to be recent
JimmyZ wait a moment
nwc10 but I think it's just tickling an old thing, as I can't nail any revision that "caused" it
JimmyZ jnthn: pastebin.com/ANpY9hav 10:25
jnthn Well, S17 one is maybe heisenbug, but the S02 one is odd. 10:26
nwc10 JimmyZ: I've never seen those two fail, so I can't suggest anything.
however, I believe that nothing in my environment is outside of ASCII
JimmyZ I think I can take a look 10:36
FROGGS that is also what I am guessing... your env might contain Chinese stuff?
then it should also fail when you run it outside of the spectest 10:37
jnthn
.oO( environment variables with Chinese characteristics )
nwc10 we used to like fa_IR.utf8, because the decimal separator was 2 octets of UTF-8
but these days it seems to be either . or , so back to one
however, ps_AF.utf8 (IIRC - Pashtun, Afgahnistan) now seems to have this wonderful property 10:38
jnthn Sounds like fun :) 10:53
10:58 Ven joined 11:01 terrence_ joined 12:17 JimmyZ joined 13:27 brrt joined 15:24 JimmyZ joined 15:43 Ven joined 16:49 oetiker joined 17:13 vendethiel joined 19:08 FROGGS joined 19:10 FROGGS_ joined 20:11 FROGGS_ joined 20:13 lizmat joined 20:29 woolfy joined 20:31 tadzik joined, xiaomiao joined, moritz joined 20:34 colomon joined 21:34 brrt joined