00:17:16 FYI: Another Redmine outage at 1630Z (about 13 minutes from now) as we try to upgrade Redmine itself 00:17:50 *0030Z 00:17:53 t i m e 00:25:51 You mean @62 .beats! 00:25:59 ha! 00:53:08 ooh.. any new features worth noting? 01:03:13 Who can tell, given the amount of Ruby tedium between here and the finish line 01:17:41 hrm.. how upset would people be if cw added '-fdiagnostics-color=always' to gcc runs iff cw's stdout is a terminal? for when you're building interactively (but keep esc codes out of nightly/mail_msg) 01:20:07 (i finally bothered to look, but i'm guessing others already knew) since it saves each compiler's output to a temp file and then writes it out, so it gets disabled 01:20:31 jbk: will it respect NO_COLOR 01:21:07 also, why do you have to force it if output is a terminal 01:21:28 Also, FYI: Redmine is probably good to go now. Let me know if you see any problems. 01:21:44 cw's stdout is a terminal, when cw invokes gcc, gcc's stdout is a file 01:22:30 Ah, to deal with running several things? 01:22:42 or if -fdiagnostics-color= is passed in, it could pass that along and not add anything 01:22:50 yeah 01:23:06 which is why it's always disabled after bldenv 01:23:45 Yeah, I think probably: don't override if already passed, don't set it if NO_COLOR is set, and that's probably fine 01:23:47 i sort of figured that's why, but it was one of those things I always noticed (why aren't I geting color errors like elsewhere?) but never quite cared enough to really look until curiousity finally got me 01:25:06 [illumos-gate] 16979 stdbit.h _Generic pieces could work in C11 -- Robert Mustacchi 01:36:19 jbk: one thing to watch out for is that make will itself redirect output to a per-job temporary file when building in parallel. Might need to peel another layer of that onion. 01:37:28 (but, yes, that sounds reasonable as long as it can be turned off -- I personally dislike colorized/angry fruit salad output) 17:22:40 rmustacc: I see a bit theory statement in usr/src/common/io/pciex/pcie.c (without looking, I"m going to guess it's from you :P) are there any other places I should look to start digging into those errors? 17:55:42 For digging into errors? 18:01:09 If that uts/common/io/pciex/pcie_fault.c. 18:29:02 "bit theory" I think you meant "big" (RM's theory statements aren't "bit". :) ) 19:01:50 oh yeah, big.. the explanation there is really good and certainly not bit 21:20:08 Hello