Re: Exit code -11 must die

2016-02-29 Thread Randell Jesup
>On 2/27/2016 9:06 PM, Randell Jesup wrote: >> months until recently it popped up a bit). Note that this failure >> *never* results in a crashdump, and I've never seen it locally, just in >> Automation. > >What we do know: > > * Exit code -11 is evidence a SIGSEGV (crash). > >This I don't know, bu

Re: Exit code -11 must die

2016-02-29 Thread Andrew Halberstadt
On 29/02/16 12:03 PM, Benjamin Smedberg wrote: On 2/27/2016 9:06 PM, Randell Jesup wrote: months until recently it popped up a bit). Note that this failure *never* results in a crashdump, and I've never seen it locally, just in Automation. What we do know: * Exit code -11 is evidence a SIG

Re: Exit code -11 must die

2016-02-29 Thread Kyle Huey
On Mon, Feb 29, 2016 at 9:03 AM, Benjamin Smedberg wrote: > On 2/27/2016 9:06 PM, Randell Jesup wrote: > >> months until recently it popped up a bit). Note that this failure >> *never* results in a crashdump, and I've never seen it locally, just in >> Automation. >> > > What we do know: > > * E

Re: Exit code -11 must die

2016-02-29 Thread Benjamin Smedberg
On 2/27/2016 9:06 PM, Randell Jesup wrote: months until recently it popped up a bit). Note that this failure *never* results in a crashdump, and I've never seen it locally, just in Automation. What we do know: * Exit code -11 is evidence a SIGSEGV (crash). This I don't know, but somebody ma

Exit code -11 must die

2016-02-27 Thread Randell Jesup
We have a raft of intermittent oranges where we get "exit code -11". I'm trying to land a patch, which is causing a largely-unrelated set of tests (identity) to generate the infamous exit code -11 problem (there's an existing intermittent filed against that test; it had disappeared for months unti