Re: [PATCH] sparse: Make -Werror turn warnigns into errors

[Thomas Graf <tgraf@suug.ch>]

On 09/24/14 at 11:24pm, Christopher Li wrote:
> In stead of patching each test case file. How about teach the
> test-suilte to be smarter? The test-suilte should change the default
> return value to none zero if there is none empty "check-error-start" and
> "check-error-end" section. In other words, if there is expected
> error output, we already guess the returns status is error.
> The test case can still use "check-exit-value" to overwrite the default
> value.
> 
> I expect that can save most of the patching to test case file.

The return value of thest will only be non zero if an actual error
has been detected. It will remain zero if only warnings have been
found. So we would need to parse the text between "check-exit-start"
and "check-error-end" for the string "error:" or something a like
that. I found that to be fragile and the explicit declaration of an
expected failure to be superior as it also verifies whether an
expected warning is properly treated as a warning or not.