[zorg] r173944 - Mark build as failing when encountering line of type: \* TEST '.' FAILED \*

[David Dean]

On 30 Jan 2013, at 12:12 PM, David Blaikie <dblaikie at gmail.com> wrote:

> On Wed, Jan 30, 2013 at 12:08 PM, David Dean <david_dean at apple.com> wrote:
>> On 30 Jan 2013, at 11:41 AM, David Blaikie <dblaikie at gmail.com> wrote:
>> 
>>> Where is this other log format coming from? It doesn't seem to be the
>>> same as the lit output, so I'd really like to make them consistent or
>>> handle them separately perhaps.
>> 
>> This is the (slightly redacted) log:
>> 
>> FAIL: LLVM :: CodeGen/CellSPU/call.ll (1205 of 8513)
>> ******************** TEST 'LLVM :: CodeGen/CellSPU/call.ll' FAILED ********************
> 
> Ah, right, so Lit does produce that normally... so what log file did I
> model my log parsing from, I wonder...
> 
> Anyway - do we have a consistent pattern for this? (perhaps taken from
> Lit's code itself as an authoritative reference) I assume we can see
> all the possible failure codes in that location & it's probably not
> worth even retrieving the particular code (why do we put that there
> when we logged it (& the name) on the line before... (or why log the
> line before).
> 
> Anyway, it'd be nice to just ensure we're dealing with one lit file
> format, match that, generate it from all the places that we want to
> claim are 'lit' & go with it.

As long as nothing breaks. ;)

-David