[LLVMdev] DejaGNU test fixes

Matthijs Kooijman - Inter-Actief matthijs.kooijman at inter-actief.net
Wed Jun 11 05:04:25 PDT 2008

> Does merely sending output to stderr legitimately constitute a test  
> failure? 
Yes and no :-)

I think that being notified of stderr output is generally a good idea. If you
really think that for a particular testcase stderr output is expected and
doesn not mean failure, that particular test can redirect stderr and things
work fine.

However, the most compelling reason for marking stderr output as a failure is
my lack of TCL skills :-) I haven't found a way to distinguish between stderr
output of the program and parsing errors of the command line. So, rather than
ignoring command line parse options, I'd rather fail on stderr output.

So, it's not a policy decision to mark stderr output as a failure, but now
that it is happening I don't think it is so bad to do so.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080611/1c3c3246/attachment.sig>

More information about the llvm-dev mailing list