[llvm-testresults] buildbot failure in smooshlab on clang-i386-darwin9

[daniel_dunbar at apple.com]

The Buildbot has detected a new failure of clang-i386-darwin9 on smooshlab.
Full details are available at:
 http://smooshlab.apple.com:8010/builders/clang-i386-darwin9/builds/13437

Buildbot URL: http://smooshlab.apple.com:8010/

Buildslave for this Build: smoosh-15.apple.com

Build Reason: 
Build Source Stamp: 114225
Blamelist: dgregor,echristo,evancheng

BUILD FAILED: failed test-clang

sincerely,
 -The Buildbot


================================================================================

CHANGES:
File: lib/Target/ARM/ARMFastISel.cpp
At: Fri 17 Sep 2010 15:30:56
Changed By: echristo
Comments: Rework arm fast isel branch and compare code.
Properties: 




Files:
 lib/CodeGen/MachineSink.cpp
 test/CodeGen/X86/lsr-reuse.ll
 test/CodeGen/X86/pr3522.ll
 test/CodeGen/X86/tail-opts.ll
At: Fri 17 Sep 2010 15:30:56
Changed By: evancheng
Comments: Teach machine sink to
1) Do forward copy propagation. This makes it easier to estimate the cost of the
   instruction being sunk.
2) Break critical edges on demand, including cases where the value is used by
   PHI nodes.
Critical edge splitting is not yet enabled by default.
Properties: 




Files:
 lib/Parse/ParseExpr.cpp
 test/FixIt/fixit-unrecoverable.cpp
 test/Index/complete-recovery.m
 test/SemaCXX/destructor.cpp
 test/SemaCXX/elaborated-type-specifier.cpp
 test/SemaObjC/crash-label.m
 test/SemaTemplate/dependent-base-classes.cpp
At: Fri 17 Sep 2010 15:30:56
Changed By: dgregor
Comments: When we run into an error parsing or type-checking the left-hand side
of a binary expression, continue on and parse the right-hand side of
the binary expression anyway, but don't call the semantic actions to
type-check. Previously, we would see the error and then, effectively,
skip tokens until the end of the statement. 

The result should be more useful recovery, both in the normal case
(we'll actually see errors beyond the first one in a statement), but
it also helps code completion do a much better job, because we do
"real" code completion on the right-hand side of an invalid binary
expression rather than completing with the recovery completion. For
example, given

  x = p->y

if there is no variable named "x", we can still complete after the p->
as a member expression. Along the recovery path, we would have
completed after the "->" as if we were in an expression context, which
is mostly useless.

Properties: 




LOGS:
Last 10 lines of 'stdio':
	Testing Time: 42.91s
	********************
	Failing Tests (1):
	    Clang :: FixIt/typo.m
	
	  Expected Passes    : 2528
	  Expected Failures  : 20
	  Unexpected Failures: 1
	make[1]: *** [all] Error 1
	make: *** [test] Error 2

Last 10 lines of 'warnings':
	1 warning and 20 errors generated.

Last 10 lines of 'fail':
	Clang :: FixIt/typo.m

Last 10 lines of 'xfail':
	Clang :: FixIt/fixit-pmem.cpp
	Clang :: FixIt/fixit-errors.c
	Clang :: Lexer/hexfloat.cpp
	Clang :: PCH/changed-files.c
	Clang :: PCH/pr4489.c
	Clang :: PCH/source-manager-stack.c
	Clang :: Parser/cxx-ambig-decl-expr-xfail.cpp
	Clang :: SemaCXX/rval-references-xfail.cpp
	Clang :: SemaObjCXX/overload.mm
	Clang :: SemaTemplate/instantiate-function-1.mm

Last 10 lines of 'typo.m':
	--
	error: 'error' diagnostics seen but not expected: 
	  Line 13: use of undeclared identifier 'str'
	1 warning and 20 errors generated.
	error: error reading '/Users/buildslave/zorg/buildbot/smooshlab/slave/build.clang-i386-darwin9/llvm/tools/clang/test/FixIt/Output/typo.m.tmp'
	1 error generated.
	--
	
	********************